Adds ipv6 local deployment to poc (quay#1187)

Co-authored-by: Steven Smith <[email protected]>

Author: stevsmit

deploy_quay/master.adoc

@@ -55,6 +55,11 @@ include::modules/ssl-testing-ui.adoc[leveloffset=+3]
 include::modules/ssl-trust-ca-podman.adoc[leveloffset=+2]
 include::modules/ssl-trust-ca-system.adoc[leveloffset=+2]
 
+//local ipv6 deployment
+include::modules/proc_deploy_quay_local_ipv6.adoc[leveloffset=+1]
+include::modules/poc-creating-dual-stack-cn.adoc[leveloffset=+2]
+include::modules/deploy-local-quay-ipv6.adoc[leveloffset=+2]
+
 include::modules/proc_deploy_quay_poc_next.adoc[leveloffset=1]
 
 ////

modules/deploy-local-quay-ipv6.adoc

@@ -0,0 +1,31 @@
+:_content-type: PROCEDURE
+[id="deploy-local-quay-ipv6"]
+= Deploying a local instance of {productname} in IPv6
+
+After you have created a new dual-stack container network, you can deploy a local instance of {productname}.
+
+.Prerequisites
+
+* You have configured Redis, your PostgreSQL database, local image storage, and creating a `config.yaml` file with the desired settings.
+
+.Procedure
+
+. In your {productname} `config.yaml` file, set the `FEATURE_LISTEN_IP_VERSION` field to `IPv6`. For example:
++
+[source,yaml]
+----
+# ...
+FEATURE_LISTEN_IP_VERSION: dual-stack
+# ...
+----
+
+. Enter the following command to start the `Quay` registry container, specifying the appropriate volumes for configuration data and local storage for image data. Note that if you are using dual-stack, you must specify explicit IPv6 port mapping when starting the container.
++
+[subs="verbatim,attributes"]
+----
+$ sudo podman run -d --rm -p "[::]:80:8080" -p "[::]:443:8443"  \
+   --name=quay \
+   -v $QUAY/config:/conf/stack:Z \
+   -v $QUAY/storage:/datastorage:Z \
+   {productrepo}/{quayimage}:{productminv}
+----

modules/poc-creating-dual-stack-cn.adoc

@@ -0,0 +1,16 @@
+:_content-type: PROCEDURE
+[id="poc-creating-dual-stack-cn"]
+= Creating a dual-stack container network
+
+Use the following procedure to create a new container network that is dual-stack.
+
+.Procedure
+
+* Unless there is a requirement that the _default_ container network use both IPv4 and IPv6, it is suggested that a _new_ container network is created that is dual-stack. As a root user, create a new container network that is dual-stack by running the following command:
++
+[source,terminal]
+----
+# podman network create ip-dual-stack --ipv6
+----
++
+With this command, new containers use this network are a natively dual-stack.

modules/proc_deploy_quay_local_ipv6.adoc

@@ -0,0 +1,13 @@
+:_content-type: CONCEPT
+[id="poc-deploy-quay-local-ipv6"]
+= Configuring the Podman CNI to use IPv6
+
+In some cases, you might want to run a local instance of {productname} to use IPv6. This setup is common for development or testing purposes.
+
+By default, the Podman network for a root user does not use IPv6, and instead defaults to use IPv4. You can configure the Podman Container Network Interface (CNI) to use both IPv4 and IPv6, which allows for a local instance of {productname} using IPv6.
+
+[discrete]
+[id="additional-resources"]
+== Additional resources
+
+* link:https://access.redhat.com/solutions/6196301[How to configure the default podman container network for the root user to use both IPv4 and IPv6].

modules/proc_deploy_quay_poc_run.adoc

@@ -119,7 +119,7 @@ Use the following procedure to deploy the `Quay` registry container.
 
 .Procedure
 
-. Enter the following command to start the `Quay` registry container, specifying the appropriate volumes for configuration data and local storage for image data:
+* Enter the following command to start the `Quay` registry container, specifying the appropriate volumes for configuration data and local storage for image data:
 +
 [subs="verbatim,attributes"]
 ----