Create Configure Knative Networking page

docs/snippets/dns.md

@@ -1,7 +1,6 @@
-You can configure DNS to prevent the need to run curl commands with a host header.
+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 expand to show instructions for configuring DNS.
-Follow the procedure for the DNS of your choice:
+The following tabs show instructions for configuring DNS. Follow the procedure for the DNS of your choice:
 
 === "Magic DNS (sslip.io)"
 
@@ -11,10 +10,5 @@ Follow the procedure for the DNS of your choice:
     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.
+    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.
 
-        In these cases, see the "Real DNS" or "No DNS" tabs.

docs/snippets/netadapter-contour.md

@@ -0,0 +1,38 @@
+Use the following steps to install and enable Contour and set it as the ingress conroller.
+
+1. Install the Knative Contour configuration:
+
+    ```bash
+    kubectl apply -f {{ artifact(org="knative-extensions", repo="net-contour", file="contour.yaml" }}
+    ```
+
+    <!-- ```bash
+    kubectl apply -f https://github.com/knative-extensions/net-contour/releases/download/knative-v1.20.0/contour.yaml
+    ```   -->
+
+1. Install the Knative Contour integration controller:
+
+    ```bash
+    kubectl apply -f https://github.com/knative-extensions/net-contour/releases/download/knative-v1.20.0/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. Verify the installation by having a pod with the base name of `contour` in the results.
+
+    ```bash
+    kubectl get pods -n knative-serving
+    ```
+
+1. Get the external IP address (FQDN) to configure DNS records:
+
+    ```bash
+    kubectl --namespace contour-external get service envoy
+    ```

docs/snippets/netadapter-gatewayapi.md

@@ -0,0 +1,42 @@
+Use the following steps to install and configure the Knative Gateway API adapter.  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. Clone the Gateway API repo:
+
+    ```bash
+    git clone https://github.com/knative-extensions/net-gateway-api.git
+    cd net-gateway-api
+    ```
+
+1. Set environment variables:
+
+    ```bash
+    export KO_DOCKER_REPO=kind.local
+    export KIND_CLUSTER_NAME=knative  # (keep this if your cluster is named "knative")
+    ```
+
+1. Deploy Gateway API resources:
+
+    ```bash
+    ko apply -f config/
+    ```
+
+1. Install the Knative Gateway API:
+
+    ```bash
+      kubectl apply -f {{ artifact(repo="net-gateway-api",org="knative-extensions",file="net-gateway-api.yaml") }}
+    ```
+
+1. Configure Knative Serving to use Knative Gateway API channel:
+
+    ```bash
+    kubectl patch configmap/config-network \
+      --namespace knative-serving \
+      --type merge \
+      --patch '{"data":{"ingress-class":"gateway-api.ingress.networking.knative.dev"}}'
+    ```
+
+1. Get the external IP address (FQDN) to configure DNS records:
+
+    ```bash
+    kubectl get gateway --all-namespaces
+    ```

docs/snippets/netadapter-istio.md

@@ -0,0 +1,44 @@
+Use the following steps to install Istio and set it as the ingress conroller.
+
+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") }}
+    ```
+
+    <!-- ```bash
+    kubectl apply -l knative.dev/crd-install=true -f https://github.com/knative-extensions/net-istio/releases/download/knative-v1.20.1/istio.yaml
+    kubectl apply -f https://github.com/knative-extensions/net-istio/releases/download/knative-v1.20.1/istio.yaml
+    ``` -->
+
+1. Install the Knative Istio controller:
+
+    ```bash
+    kubectl apply -f {{ artifact(repo="net-istio",file="net-istio.yaml") }}
+    ```
+
+    <!-- ```bash
+    kubectl apply -f https://github.com/knative/net-istio/releases/download/knative-v1.20.1/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. Verify the installation by having pods with the base name of `istio` and `istio-webhook` in the results.
+
+    ```bash
+    kubectl get pods -n knative-serving
+    ```
+
+1. Get the external IP address (FQDN) to configure DNS records:
+
+    ```bash
+    kubectl --namespace istio-system get service istio-ingressgateway
+    ```

docs/snippets/netadapter-kourier.md

@@ -0,0 +1,32 @@
+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",file="kourier.yaml") }}
+    ```
+
+    <!-- ```bash
+    kubectl apply -f https://github.com/knative/net-kourier/releases/latest/download/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. Verify the installation by having pods with the base name of `kourier-controller` and `kourier-gateway` in the results.
+
+    ```bash
+    kubectl get pods -n knative-serving
+    ```
+
+1. Get the external IP address (FQDN) to configure DNS records:
+
+    ```bash
+    kubectl --namespace kourier-system get service kourier
+    ```

docs/snippets/no-dns.md

@@ -1,7 +1,3 @@
-<!-- Referenced by:
-- 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,

docs/versioned/.nav.yml

@@ -267,6 +267,7 @@ nav:
         - Configure high-availability components: serving/config-ha.md
         - Exclude namespaces from the Knative webhook: serving/webhook-customizations.md
         - Networking Options:
+          - Configure Knative networking: serving/config-network-adapters.md
           - Configure the ingress gateway: serving/setting-up-custom-ingress-gateway.md
           - Configure domain names: serving/using-a-custom-domain.md
           - Istio Authorization: serving/istio-authorization.md