Create Configure Knative Networking page (#6518)

* Create config-network-adapters.md

Create file - table test

* Added Nav

Added Nav and fixed H1

* Update config-network-adapters.md

Formatting test

* Update config-network-adapters.md

More writing

* Added snippet file for Kourier

Snippet testing

* Update config-network-adapters.md

snippet testing

* Update config-network-adapters.md

Snippet name fix

* Snippet fix

Formatting tests

* Update config-network-adapters.md

Formatting fix

* Update config-network-adapters.md

Test

* Update config-network-adapters.md

Rebuild

* Added Contour snippet

Formmating

* Update config-network-adapters.md

Typo fix

* Added istio and gateway api snippet files

Formatting

* Writing and snippet work

Updates

* Misc fixes

Snippet formatting

* Link fixes

Misc edits

* Update netadapter-istio.md

Link issue fix

* Tab work

Added tabs for Network layer setup

* Update config-network-adapters.md

Minor edit to rebuild

* Update config-network-adapters.md

tab test

* Update config-network-adapters.md

More writing and tab test for architecture section

* Title and edits

Title change and format fix

* Update config-network-adapters.md

indented mermaid test

* Update config-network-adapters.md

Mermaid tab test

* Update config-network-adapters.md

undid test

* Update config-network-adapters.md

Mermaid fix

* Update config-network-adapters.md

Tab test

* Update config-network-adapters.md

More mermaid testing

* Update config-network-adapters.md

mermaid work

* Update config-network-adapters.md

Formatting

* Update config-network-adapters.md

More writing

* Update config-network-adapters.md

H4s instead of H3s

* Update config-network-adapters.md

Mermaid tweaks

* Update config-network-adapters.md

tab test

* Writing and structuring

Trying out just one tab set

* Update config-network-adapters.md

Formatting fixes

* Update config-network-adapters.md

Minor edit to rebuild

* Update netadapter-gatewayapi.md

Formatting test

* Formatting tests

* Update config-network-adapters.md

Formatting test

* Update config-network-adapters.md

Format fix

* Update config-network-adapters.md

test

* Update config-network-adapters.md

Put back `Verify controller installations`

* Update config-network-adapters.md

Formatting

* Update config-network-adapters.md

Minor fix

* Update config-network-adapters.md

Code format fix

* Added Ingress Gateway tab

More writing

* Update config-network-adapters.md

Formatting fix

* More writing

Consistency edits

* Update config-network-adapters.md

Format fix

* Update config-network-adapters.md

Refinement edits

* Misc fixes

Fixes and refinements

* Small edit to rebuild

* Update config-network-adapters.md

Refinement edits

* Update config-network-adapters.md

Minor edit to rebuild

* Misc updates

Copy and refinement edits

* Update config-network-adapters.md

Added note about IBM Z and IBM Power platforms and Kourier.

* Update config-network-adapters.md

Fixed link

* Update config-network-adapters.md

Format fix

* Update netadapter-gatewayapi.md

Updated Gateway API steps

* Update config-network-adapters.md

Fixed typos and tweaking

* Update config-network-adapters.md

Minor edit to rebuild

* Update config-network-adapters.md

Consistency edits

* Update config-network-adapters.md

Link fix

* Update docs/snippets/dns.md

Co-authored-by: Evan Anderson <evan.k.anderson@gmail.com>

* Processed reviewer edits

* Misc edits

Moved page up in Nav, moved 'Detect current state' section down. Also format edits.

* Update config-network-adapters.md

H3 to H2 - Determine current state

* Update docs/versioned/serving/config-network-adapters.md

Co-authored-by: Evan Anderson <evan.k.anderson@gmail.com>

* Reviewer udpates

Removed code snippets - will only be in yaml installation
Nav change
Diagram work

* Update config-network-adapters.md

Minor edit to rebuild

* Update config-network-adapters.md

Test edits to rebuild

* Update config-network-adapters.md

Build test

* Update config-network-adapters.md

Build issue with adjacent charts?

* Update config-network-adapters.md

chart test

* Update config-network-adapters.md

Test

* Update config-network-adapters.md

Mermaid chart formatting

* Update config-network-adapters.md

Chart fix

* Update config-network-adapters.md

Chart fix

* Update config-network-adapters.md

Chart formatting

* Update docs/snippets/netadapter-kourier.md

Co-authored-by: David Simansky <dsimansk@redhat.com>

* Update config-network-adapters.md

chart work

* Update config-network-adapters.md

chart work

* Chart work and misc fixes

* Misc updates

Formatting and installation snippets

* Update config-network-adapters.md

indentation test

* Gateway additions and misc

various updates

* Update config-network-adapters.md

Minor edit to rebuild

* Update config-network-adapters.md

Minor edits to rebuild

* Update config-network-adapters.md

tab fixes and minor edits

* Update config-network-adapters.md

Minor edit to rebuild

* Update config-network-adapters.md

Restructuring refinements

* Update config-network-adapters.md

Refinements

* Update config-network-adapters.md

Grammer refinements

* Tab test with snippets

* Configured snippets

Configured snippets to conform with install-serving-with-yaml

* Update install-serving-with-yaml.md

Provided guidance to refer to the configuration topic

* Snippet code formatting

* Update install-serving-with-yaml.md

minor edits

* Update install-serving-with-yaml.md

Link fix

* Update docs/versioned/serving/config-network-adapters.md

Co-authored-by: Evan Anderson <evan.k.anderson@gmail.com>

* Update docs/versioned/serving/config-network-adapters.md

Co-authored-by: Evan Anderson <evan.k.anderson@gmail.com>

* Update docs/versioned/serving/config-network-adapters.md

Co-authored-by: Evan Anderson <evan.k.anderson@gmail.com>

* Update docs/versioned/serving/config-network-adapters.md

Co-authored-by: Evan Anderson <evan.k.anderson@gmail.com>

* Update config-network-adapters.md

Processed reviewer edits

* Update config-network-adapters.md

Review edits cont'd.

* Update config-network-adapters.md

mermaid tweaks

* Update config-network-adapters.md

Mermaid fixes

* Update config-network-adapters.md

Mermaid adjustments

* Snippet references and fixes

Also name change to "Configure Istio's ingress gateway"

* Misc edits

And tab test with snippet references

* Update install-serving-with-yaml.md

tabs with snippet references fix

* Update install-serving-with-yaml.md

tab test again

* Snippet and Tab fixes

Formatting tasks

* Tab fixes

* Tab fixes and reviewer edits

Misc fixes and edits

* tab tweaks

* tab and include test

* tab include test

testing...

* tab test

* A hopeful test

* Tab test with indent filter

* Indent test

* Test edit to rebuild

* Install snippets and DNS snippets

Indentation formatting, wordsmithing

* Update install-serving-with-yaml.md

minor edit to rebuld

* file name fix

* Format fixes and rerognization

Misc edits

* formatting fixes

* Link improvment

minor edit

* link format edits

Edit to rebuild

* Update netadapter-gatewayapi.md

Steps rearrangement

* Processed reviewer edits

* Chart updates

And misc edits

* Added diagram headings

* minor edit to rebuild

* Copy edits

* minor edit to rebuild

* link improvement

* Removed erroneous para

* link fix

* link fix again

* Link tweak

* typo fix

* Link enhanements

* Update knative-with-operators.md

DNS section fix

* Update real-dns-operator.md

Added snippet reference of the file where its used.

* Update config-network-adapters.md

Small edit to rebuild

---------

Co-authored-by: Evan Anderson <evan.k.anderson@gmail.com>
Co-authored-by: David Simansky <dsimansk@redhat.com>

Author: 3 people

docs/snippets/dns.md

@@ -1,20 +1,11 @@
-You can configure DNS to prevent the need to run curl commands with a host header.
+<!-- Referenced by:
+- install/operator/knative-with-operators.md
+- install/yaml-install/serving/install-serving-with-yaml.md
+-->
+Knative provides a Kubernetes Job called `default-domain` that configures Knative Serving to use [sslip.io](http://sslip.io) as the default DNS suffix.
 
-The following tabs expand to show instructions for configuring DNS.
-Follow the procedure for the DNS of your choice:
+```bash
+kubectl apply -f {{artifact(repo="serving",file="serving-default-domain.yaml")}}
+```
 
-=== "Magic DNS (sslip.io)"
-
-    Knative provides a Kubernetes Job called `default-domain` that configures Knative Serving to use [sslip.io](http://sslip.io) as the default DNS suffix.
-
-    ```bash
-    kubectl apply -f {{artifact(repo="serving",file="serving-default-domain.yaml")}}
-    ```
-
-    !!! warning
-        This will only work if the cluster `LoadBalancer` Service exposes an
-        IPv4 address or hostname, so it will not work with IPv6 clusters or local setups
-        like minikube unless [`minikube tunnel`](https://minikube.sigs.k8s.io/docs/commands/tunnel/)
-        is running.
-
-        In these cases, see the "Real DNS" or "No DNS" tabs.
+This configuration works only if the cluster `LoadBalancer` Service exposes an IPv4 address or hostname. It does not work with IPv6 clusters or local setups such as minikube unless the [`minikube tunnel`](https://minikube.sigs.k8s.io/docs/commands/tunnel/) is running.

docs/snippets/netadapter-contour.md

@@ -0,0 +1,31 @@
+<!-- Referenced by:
+- install/yaml-install/serving/install-serving-with-yaml.md
+-->
+Use the following steps to install and enable Contour and set it as the ingress controller.
+
+1. Install the Knative Contour configuration:
+
+    ```bash
+    kubectl apply -f {{ artifact(repo="net-contour",org="knative-extensions",file="contour.yaml")}}
+    ```
+
+1. Install the Knative Contour integration controller:
+
+    ```bash
+    kubectl apply -f {{ artifact(repo="net-contour",org="knative-extensions",file="net-contour.yaml")}}
+    ```
+
+1. Configure Knative Serving to use Contour:
+
+    ```bash
+        kubectl patch configmap/config-network \
+        --namespace knative-serving \
+        --type merge \
+        --patch '{"data":{"ingress-class":"contour.ingress.networking.knative.dev"}}'
+    ```
+
+1. Get the external IP address (FQDN) to later configure DNS:
+
+    ```bash
+    kubectl --namespace contour-external get service envoy
+    ```

docs/snippets/netadapter-gatewayapi.md

@@ -0,0 +1,62 @@
+<!-- Referenced by:
+- install/yaml-install/serving/install-serving-with-yaml.md
+-->
+This component is in beta. For the latest information including supported implementations, see the [Knative net-gateway-api](https://github.com/knative-extensions/net-gateway-api).
+
+Use the following steps to install and configure the Knative Gateway API controller.  Note that you need to have a [Gateway API implementation](https://gateway-api.sigs.k8s.io/implementations/) installed in your cluster.  The Knative team currently tests the Istio, Contour, and Envoy-Gateway implementations of Gateway API.
+
+1. Install the Knative Gateway API:
+
+    ```bash
+    kubectl apply -f {{ artifact(repo="net-gateway-api",org="knative-extensions",file="net-gateway-api.yaml") }}
+    ```
+
+    <!-- TODO: Alternatively, you can use `contour-gateway.yaml` or `istio-gateway.yaml`.  -->
+
+1. Configure Gateway resources for external ("north-south") and local ("east-west") Knative traffic. If you do not need separate routing for local traffic (or [private Knative services](../../../serving/services/private-services.md)), you can use the external Gateway for both.
+
+    Knative verifies traffic settings according to the Kubernetes namespace, the name of the Gateways, and an underlying DNS name such as a Kubernetes service DNS name that corresponds to the Gateway.
+
+    ```bash
+    cat <<EOF | kubectl apply -f -
+    apiVersion: v1
+    kind: ConfigMap
+    metadata:
+      name: config-gateway
+      namespace: knative-serving
+    data:
+      external-gateways: |
+        - name: knative-ingress-gateway  # Name of the external Gateway resource
+          namespace: knative-serving     # Namespace where the Gateway is deployed
+          service: knative-ingress-service.knative-serving.svc.cluster.local  # backing Service FQDN
+      local-gateways: |
+        - name: knative-local-gateway    # Name of the local Gateway resource
+          namespace: knative-serving     # Namespace where the Gateway is deployed
+          service: knative-local-service.knative-serving.svc.cluster.local    # backing Service FQDN
+    EOF
+    ```
+
+1. Configure Knative Serving to use the Knative Gateway API ingress class:
+
+    ```bash
+    kubectl patch configmap/config-network \
+      --namespace knative-serving \
+      --type merge \
+      --patch '{"data":{"ingress-class":"gateway-api.ingress.networking.knative.dev"}}'
+    ```
+
+1. Verify the `config-gateway` ConfigMap:
+
+    ```bash
+    kubectl describe configmaps config-gateway -n knative-serving
+    ```
+
+    Examine the values for the `externals-gateways` and `local-gateways` keys.
+
+1. Get the external IP address (FQDN) to configure DNS records:
+
+    ```bash
+    kubectl get gateway --all-namespaces
+    ```
+
+    Look for the external Gateway (`knative-ingress-gateway`) to get status and address for DNS configurations.

docs/snippets/netadapter-istio.md

@@ -0,0 +1,32 @@
+<!-- Referenced by:
+- install/yaml-install/serving/install-serving-with-yaml.md
+-->
+Use the following steps to install Istio and set it as the ingress controller.
+    
+1. Install a properly configured Istio:
+
+    ```bash
+    kubectl apply -l knative.dev/crd-install=true -f {{ artifact(repo="net-istio",org="knative-extensions",file="istio.yaml") }}
+    kubectl apply -f {{ artifact(repo="net-istio",org="knative-extensions",file="istio.yaml") }}
+    ```
+
+1. Install the Knative Istio controller:
+
+    ```bash
+    kubectl apply -f {{ artifact(repo="net-istio",org="knative-extensions", file="net-istio.yaml") }}
+    ```
+
+1. Configure the `config-network` ConfigMap to use Istio:
+
+    ```bash
+        kubectl patch configmap/config-network \
+        --namespace knative-serving \
+        --type merge \
+        --patch '{"data":{"ingress-class":"istio.ingress.networking.knative.dev"}}'
+    ```
+
+1. Get the external IP address (FQDN) to later configure DNS:
+
+    ```bash
+    kubectl --namespace istio-system get service istio-ingressgateway
+    ```

docs/snippets/netadapter-kourier.md

@@ -0,0 +1,25 @@
+<!-- Referenced by:
+- install/yaml-install/serving/install-serving-with-yaml.md
+-->
+Use the following steps to install Kourier and set it as the ingress controller.
+    
+1. Install the Knative Kourier controller:
+
+    ```bash
+        kubectl apply -f {{ artifact(repo="net-kourier",org="knative-extensions", file="kourier.yaml") }}
+    ```
+
+1. Configure Knative Serving to use Kourier by default:
+
+    ```bash
+    kubectl patch configmap/config-network \
+    --namespace knative-serving \
+    --type merge \
+    --patch '{"data":{"ingress-class":"kourier.ingress.networking.knative.dev"}}'
+    ```
+
+1. Get the external IP address (FQDN) to later configure DNS:
+
+    ```bash
+    kubectl --namespace kourier-system get service kourier
+    ```

docs/snippets/no-dns.md

@@ -2,40 +2,42 @@
 - install/operator/knative-with-operators.md
 - install/yaml-install/serving/install-serving-with-yaml.md
 -->
-=== "No DNS"
-
-    If you are using `curl` to access [the sample applications](/docs/getting-started/first-service/), or your own Knative app, and are unable to use the "Magic DNS (sslip.io)" or "Real DNS" methods, there is a temporary approach. This is useful for those who wish to evaluate Knative without altering their DNS configuration, as per the "Real DNS" method, or cannot use the "Magic DNS" method due to using,
-    for example, minikube locally or IPv6 clusters.
-
-    To access your application using `curl` using this method:
-
-    1. Configure Knative to use a domain reachable from outside the cluster:
-      ```bash
-      kubectl patch configmap/config-domain \
-            --namespace knative-serving \
-            --type merge \
-            --patch '{"data":{"example.com":""}}'
-      ```
-
-    1. After starting your application, get the URL of your application:
-      ```bash
-      kubectl get ksvc
-      ```
-      The output should be similar to:
-      ```bash
-      NAME            URL                                        LATESTCREATED         LATESTREADY           READY   REASON
-      helloworld-go   http://helloworld-go.default.example.com   helloworld-go-vqjlf   helloworld-go-vqjlf   True
-      ```
-
-    1. Instruct `curl` to connect to the External IP or CNAME defined by the
-       networking layer mentioned in section 3, and use the `-H "Host:"` command-line
-       option to specify the Knative application's host name.
-       For example, if the networking layer defines your External IP and port to be `http://192.168.39.228:32198` and you wish to access the `helloworld-go` application mentioned earlier, use:
-       ```bash
-       curl -H "Host: helloworld-go.default.example.com" http://192.168.39.228:32198
-       ```
-       In the case of the provided `helloworld-go` sample application, using the default configuration, the output is:
-       ```
-       Hello Go Sample v1!
-       ```
-       Refer to the "Real DNS" method for a permanent solution.
+If you are using `curl` to access [the sample applications](/docs/getting-started/first-service/), or your own Knative app, and are unable to use the "Magic DNS (sslip.io)" or "Real DNS" methods, you can evaluate Knative without altering your DNS configuration. You might have this need if minikube locally or IPv6 clusters.
+
+To access your application using `curl` using this method:
+
+1. Configure Knative to use a domain reachable from outside the cluster:
+
+  ```bash
+  kubectl patch configmap/config-domain \
+        --namespace knative-serving \
+        --type merge \
+        --patch '{"data":{"example.com":""}}'
+  ```
+
+1. After starting your application, get the URL of your application:
+
+  ```bash
+  kubectl get ksvc
+  ```
+
+  The output should be similar to:
+
+  ```bash
+  NAME            URL                                        LATESTCREATED         LATESTREADY           READY   REASON
+  helloworld-go   http://helloworld-go.default.example.com   helloworld-go-vqjlf   helloworld-go-vqjlf   True
+  ```
+
+1. Instruct `curl` to connect to the External IP or CNAME defined by the networking layer mentioned in section 3, and use the `-H "Host:"` command-line option to specify the Knative application's host name. For example, if the networking layer defines your External IP and port to be `http://192.168.39.228:32198` and you wish to access the `helloworld-go` application mentioned earlier, use:
+
+    ```bash
+    curl -H "Host: helloworld-go.default.example.com" http://192.168.39.228:32198
+    ```
+
+    In the case of the provided `helloworld-go` sample application, using the default configuration, the output is:
+
+    ```bash
+    Hello Go Sample v1!
+    ```
+
+    Refer to the "Real DNS" method for a permanent solution.

docs/snippets/real-dns-operator.md

@@ -1,3 +1,6 @@
+<!-- Referenced by:
+- install/operator/knative-with-operators.md
+-->
 === "Real DNS"
 
     To configure DNS for Knative, take the External IP

docs/snippets/real-dns-yaml.md

@@ -1,30 +1,28 @@
-=== "Real DNS"
+<!-- Referenced by:
+- install/yaml-install/serving/install-serving-with-yaml.md
+-->
+To configure DNS for Knative, take the External IP
+or CNAME from setting up networking, and configure it with your DNS provider as
+follows:
 
-    To configure DNS for Knative, take the External IP
-    or CNAME from setting up networking, and configure it with your DNS provider as
-    follows:
+- If the networking layer produced an External IP address, then configure a wildcard `A` record for the domain. In the following example, `knative.example.com` is the domain suffix for a cluster.
 
-    - If the networking layer produced an External IP address, then configure a
-      wildcard `A` record for the domain:
+    ```bash
+    *.knative.example.com == A 35.233.41.212
+    ```
 
-        ```
-        # Here knative.example.com is the domain suffix for your cluster
-        *.knative.example.com == A 35.233.41.212
-        ```
+- If the networking layer produced a CNAME, then configure a CNAME record for the domain. In the following example, `knative.example.com` is the domain suffix for a cluster.
 
-    - If the networking layer produced a CNAME, then configure a CNAME record for the domain:
+    ```bash
+    *.knative.example.com == CNAME a317a278525d111e89f272a164fd35fb-1510370581.eu-central-1.elb.amazonaws.com
+    ```
 
-        ```
-        # Here knative.example.com is the domain suffix for your cluster
-        *.knative.example.com == CNAME a317a278525d111e89f272a164fd35fb-1510370581.eu-central-1.elb.amazonaws.com
-        ```
+- After your DNS provider has been configured, direct Knative to use that domain:
 
-    - Once your DNS provider has been configured, direct Knative to use that domain:
-
-        ```yaml
-        # Replace knative.example.com with your domain suffix
-        kubectl patch configmap/config-domain \
-          --namespace knative-serving \
-          --type merge \
-          --patch '{"data":{"knative.example.com":""}}'
-        ```
+    ```yaml
+    # Replace knative.example.com with your domain suffix
+    kubectl patch configmap/config-domain \
+      --namespace knative-serving \
+      --type merge \
+      --patch '{"data":{"knative.example.com":""}}'
+    ```

docs/versioned/.nav.yml

@@ -267,7 +267,8 @@ nav:
         - Configure high-availability components: serving/config-ha.md
         - Exclude namespaces from the Knative webhook: serving/webhook-customizations.md
         - Networking Options:
-          - Configure the ingress gateway: serving/setting-up-custom-ingress-gateway.md
+          - Configure Knative networking: serving/config-network-adapters.md
+          - Configure Istio's ingress gateway: serving/setting-up-custom-ingress-gateway.md
           - Configure domain names: serving/using-a-custom-domain.md
           - Istio Authorization: serving/istio-authorization.md
           - Extending Queue Proxy image with QPOptions: serving/queue-extensions.md

docs/versioned/install/operator/knative-with-operators.md

@@ -298,9 +298,22 @@ Knative Serving with different ingresses:
 
 ### Configure DNS
 <!-- These are snippets from the docs/snippets directory -->
+You can configure DNS to avoid specifying the host header in curl commands, or to access the content with a web browser.
+
+The following tabs show instructions for configuring DNS. Follow the procedure for the DNS of your choice.
+
+=== "Magic DNS (sslip.io)"
+{% filter indent(width=4) %}
 {% include "dns.md" %}
+{% endfilter %}
+=== "Real DNS"
+{% filter indent(width=4) %}
 {% include "real-dns-operator.md" %}
+{% endfilter %}
+=== "No DNS"
+{% filter indent(width=4) %}
 {% include "no-dns.md" %}
+{% endfilter %}
 
 ## Install Knative Eventing