Create Configure Knative Networking page #6518

iRaindrop · 2025-11-19T05:58:48Z

The content for the Kourier, Contour, Gateway API, and Istio is could be helpful consolidated as opposed to separate install and config topics.

Proposed Changes

Create "Configure network adapters" under "Administration->Configuring Knative->Networking options

Create file - table test

netlify · 2025-11-19T05:58:54Z

✅ Deploy Preview for knative ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	`39b879a`
🔍 Latest deploy log	https://app.netlify.com/projects/knative/deploys/6934c0392cbf980008136524
😎 Deploy Preview	https://deploy-preview-6518--knative.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Added Nav and fixed H1

Formatting test

More writing

Snippet testing

snippet testing

Snippet name fix

Formatting tests

Formatting fix

Test

Rebuild

Formmating

Typo fix

Formatting

Updates

Snippet formatting

Misc edits

Link issue fix

Added tabs for Network layer setup

Minor edit to rebuild

Fixes and refinements

Refinement edits

Minor edit to rebuild

Copy and refinement edits

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

Fixed link

Format fix

iRaindrop · 2025-12-01T19:52:20Z

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

+
+    The Knative `net-kourier` ingress is installed with Knative Serving. Kourier is a lightweight alternative for the Istio ingress as its deployment consists only of an envoy proxy and a control plane. If Kourier is satisfactory, no further configurations are required.
+
+    Kourier is the only supported ingress controller for the IBM Z and IBM Power platforms, and requires additional steps as described in [Install Serving with YAML on IBM-Z and IBM-P](/versioned/install/yaml-install/serving/install-serving-with-yaml-on-IBM-Z-and-IBM-P.md).


The link to install-serving-with-yaml-on-IBM-Z-and-IBM-P.md returns a 404 because it is not yet in the Nav.

This should be a relative link, e.g. ../install/yaml-install/serving/install-serving-with-yaml-on-IBM-Z-and-IBM-P.yaml.

Absolute links like this won't work when we build the different documentation versions, and they wouldn't work right between newer and older documentation versions even if you got the URL to line up at one point in time.

iRaindrop · 2025-12-01T19:58:24Z

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

+        Revision --> KIGW
+    ```
+
+    Knative has a default Istio integration without the full-feature service mesh. The `knative-ingress-gateway` in the `knative-serving` namespace is a shared Istio gateway resource that handles all incoming (north-south) traffic to Knative services. This gateway points to the underlying `istio-ingressgateway` service in the `istio-system` namespace. You can replace this gateway with one of your own, see [Configuring the Ingress gateway](setting-up-custom-ingress-gateway.md).


Decision to make - bring the topic into this tab or not?

iRaindrop · 2025-12-01T20:01:02Z

docs/snippets/netadapter-istio.md

@@ -0,0 +1,35 @@
+Use the following steps to install Istio and set it as the ingress conroller.
+
+1. Install a properly configured Istio:


The artifact "macros" are not rendering to provide the URL. I wasn't able to find this one.

You may need a space between ) }} for the macro to work. I can take a look this weekend.

iRaindrop · 2025-12-01T20:06:13Z

docs/snippets/netadapter-istio.md

+    kubectl apply -f {{ artifact(repo="net-istio",file="net-istio.yaml")}}
+    ```
+
+<!-- 1. Set the `config-network` ConfigMap to use Istio:


I added this ConfigMap patch step that might not be correct. Or does Istio make the ingress controller connection without the ConfigMap?

I believe that Istio may be the default value if one is not set, but doing this explicitly shouldn't hurt.

Cali0707 · 2025-12-01T20:25:40Z

/assign @dprotaso @evankanderson

Updated Gateway API steps

knative-prow · 2025-12-01T23:53:51Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: iRaindrop
Once this PR has been reviewed and has the lgtm label, please ask for approval from dprotaso. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

iRaindrop · 2025-12-02T01:26:43Z

docs/snippets/netadapter-gatewayapi.md

+      kubectl apply -f {{ artifact(repo="net-gateway-api",org="knative-extensions",file="net-gateawy-api.yaml")}}
+    ```
+
+1. Configure Knative Serving to use Knative Gateway API channel:


Is channel the right word? Doesn't the ConfigMap need to configure the underlying ingress controller?

Knative Serving reads the configmap, so updating the ConfigMap configures Knative Serving. (This usage is correct.)

Fixed typos and tweaking

Minor edit to rebuild

Consistency edits

iRaindrop · 2025-12-04T18:06:45Z

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

+
+Review the following tabs to determine the optimal networking layer for your cluster. For most users, the Kourier ingress controller is sufficient in conjunction the default Istio gateway, which is also included in the Knative Serving installation. You can expand your capabilities with the Contour ingress, a full-feature service mesh with Istio, and the Kubernetes Gateway API.
+
+=== "Kourier"


A little context on these mermaid charts. Evan created the one for Gateway API and I did the others with AI help and I also added the Controller to the Gateway API.

Hence, they need tech reviewed as they could be misleading!

evankanderson

I got to this much later than I intended to (and I need to update the charts). A few corrections to the first half, and I may need to actually get out a cluster and cycle through the gateways for the details on each one.

docs/snippets/dns.md

evankanderson · 2025-12-06T00:17:37Z

docs/snippets/netadapter-contour.md

+1. Install the Knative Contour controller:
+
+    ```bash
+    kubectl apply -f https://github.com/knative/net-kourier/releases/latest/download/kourier.yaml


We have a macro which will use the same version as the documentation:

Suggested change

kubectl apply -f https://github.com/knative/net-kourier/releases/latest/download/kourier.yaml

kubectl apply -f {{ artifact(org="knative-extensions", repo="net-kourier", file="kourier.yaml" }}

Although, I'm realizing this should probably be net-contour and contour.yaml...

evankanderson · 2025-12-06T00:18:51Z

docs/snippets/netadapter-gatewayapi.md

+      kubectl apply -f {{ artifact(repo="net-gateway-api",org="knative-extensions",file="net-gateawy-api.yaml")}}
+    ```
+
+1. Configure Knative Serving to use Knative Gateway API channel:


Knative Serving reads the configmap, so updating the ConfigMap configures Knative Serving. (This usage is correct.)

evankanderson · 2025-12-06T00:19:38Z

docs/snippets/netadapter-istio.md

@@ -0,0 +1,35 @@
+Use the following steps to install Istio and set it as the ingress conroller.
+
+1. Install a properly configured Istio:


You may need a space between ) }} for the macro to work. I can take a look this weekend.

evankanderson · 2025-12-06T00:20:05Z

docs/snippets/netadapter-istio.md

+    kubectl apply -f {{ artifact(repo="net-istio",file="net-istio.yaml")}}
+    ```
+
+<!-- 1. Set the `config-network` ConfigMap to use Istio:


I believe that Istio may be the default value if one is not set, but doing this explicitly shouldn't hurt.

evankanderson · 2025-12-06T00:21:33Z

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

+kubectl get pods -n knative-serving
+```
+
+The ingress controllers, that have been tested for Knative, have the following base names:


The commas here don't seem quite right.

Maybe phrase this as the "The Knative team tests the following ingress controllers:"?

evankanderson · 2025-12-06T00:23:24Z

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

+- Contour: `contour-*`
+- Istio: `istio-webhook-*`. The main Istio control plane pods such as `istiod-*` are in the `istio-system` namespace. Knative adds the `istio-webhook-*` pod in the `knative-serving` namespace when Istio is the chosen networking layer.
+
+The `network-config` ConfigMap sets which controller to use with the ingress controller key. This key is patched with the name of any new controller. See [Changing the ingress controller](#change-the-controller) for important information about using this key.


This is actually slightly different -- each ingress controller only manages ingress objects that are annotated with its key. Knative Serving uses a default value of the key based on the network-config ConfigMap. So this is somewhat of a cooperative process between the ingress controller and the core Knative controller.

(The end result is effectively the same, but the mechanism is different, which seemed important to correct in the documentation.)

evankanderson · 2025-12-06T00:24:16Z

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

+
+## Network layer options
+
+Review the following tabs to determine the optimal networking layer for your cluster. For most users, the Kourier ingress controller is sufficient in conjunction the default Istio gateway, which is also included in the Knative Serving installation. You can expand your capabilities with the Contour ingress, a full-feature service mesh with Istio, and the Kubernetes Gateway API.


Folks shouldn't need both Kourier and Istio -- one or the other should be sufficient, depending on need.

evankanderson · 2025-12-06T00:26:33Z

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

+      look: neo
+    ---
+    flowchart LR
+    K1["Knative<br>net-kourier"] -- creates --> K2["Ingress&nbsp;objects"]


"Ingress" is confusing here, as Kubernetes has an "Ingress" object type which is different from the Knative networking.internal.knative.dev Ingress type. We called it "Ingress" because it was what we wanted Ingress to be, and every actual Ingress implementation had a different name for the "better Ingress" implementation.

We generally refer to the Knative version of Ingress from networking.internal as "KIngress".

evankanderson · 2025-12-06T00:28:54Z

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

+
+    The Kourier ingress controller, `net-kourier`, is installed with Knative Serving. Kourier is a lightweight alternative for the Istio ingress as its deployment consists only of an envoy proxy and a control plane. If Kourier is satisfactory, no further configurations are required.
+
+    Kourier is the only supported ingress controller for the IBM Z and IBM Power platforms, and requires additional steps as documented in [Install Serving with YAML on IBM-Z and IBM-P](/versioned/install/yaml-install/serving/install-serving-with-yaml-on-IBM-Z-and-IBM-P.md).


We should make clear that Kourier is a perfectly fine choice for all platforms, but for these IBM platforms, it's the only option.

Link fix

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

Create config-network-adapters.md

cbc1aa6

Create file - table test

knative-prow bot requested review from mmejia02 and nainaz November 19, 2025 05:58

knative-prow bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Nov 19, 2025

iRaindrop marked this pull request as draft November 19, 2025 05:59

knative-prow bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 19, 2025

iRaindrop added 3 commits November 18, 2025 22:00

Added Nav

14b81f4

Added Nav and fixed H1

Update config-network-adapters.md

3b315cb

Formatting test

Update config-network-adapters.md

9a212b2

More writing

knative-prow bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Nov 19, 2025

iRaindrop added 10 commits November 19, 2025 23:58

Added snippet file for Kourier

2300e4f

Snippet testing

Update config-network-adapters.md

e6167d0

snippet testing

Update config-network-adapters.md

d283146

Snippet name fix

Snippet fix

5062101

Formatting tests

Update config-network-adapters.md

916f3b4

Formatting fix

Update config-network-adapters.md

81fd46e

Test

Update config-network-adapters.md

d10ab27

Rebuild

Added Contour snippet

9aec3ac

Formmating

Update config-network-adapters.md

1c48767

Typo fix

Added istio and gateway api snippet files

205ecae

Formatting

knative-prow bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Nov 22, 2025

iRaindrop added 6 commits November 22, 2025 19:19

Writing and snippet work

310d9eb

Updates

Misc fixes

84f0b03

Snippet formatting

Link fixes

92d24f1

Misc edits

Update netadapter-istio.md

55a8c41

Link issue fix

Tab work

e35130c

Added tabs for Network layer setup

Update config-network-adapters.md

77cb4b8

Minor edit to rebuild

iRaindrop added 8 commits November 30, 2025 13:52

Misc fixes

1eeda2e

Fixes and refinements

Small edit to rebuild

614e293

Update config-network-adapters.md

ee0d3f0

Refinement edits

Update config-network-adapters.md

d70fae5

Minor edit to rebuild

Misc updates

aa5c536

Copy and refinement edits

Update config-network-adapters.md

1425f02

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

Update config-network-adapters.md

6659e07

Fixed link

Update config-network-adapters.md

9059d0d

Format fix

iRaindrop commented Dec 1, 2025

View reviewed changes

iRaindrop marked this pull request as ready for review December 1, 2025 20:08

knative-prow bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 1, 2025

knative-prow bot requested review from Cali0707 and skonto December 1, 2025 20:08

knative-prow bot assigned dprotaso and evankanderson Dec 1, 2025

Update netadapter-gatewayapi.md

1d76ef9

Updated Gateway API steps

iRaindrop commented Dec 2, 2025

View reviewed changes

iRaindrop added 3 commits December 2, 2025 09:20

Update config-network-adapters.md

7c0cb5d

Fixed typos and tweaking

Update config-network-adapters.md

d21ff02

Minor edit to rebuild

Update config-network-adapters.md

89a5b3c

Consistency edits

iRaindrop commented Dec 4, 2025

View reviewed changes

evankanderson reviewed Dec 6, 2025

View reviewed changes

Update config-network-adapters.md

e1b403e

Link fix

iRaindrop changed the title ~~Create Configure Network Adapters page~~ Create Configure Knative Networking page Dec 6, 2025

Update docs/snippets/dns.md

39b879a

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


		The Knative `net-kourier` ingress is installed with Knative Serving. Kourier is a lightweight alternative for the Istio ingress as its deployment consists only of an envoy proxy and a control plane. If Kourier is satisfactory, no further configurations are required.

		Kourier is the only supported ingress controller for the IBM Z and IBM Power platforms, and requires additional steps as described in [Install Serving with YAML on IBM-Z and IBM-P](/versioned/install/yaml-install/serving/install-serving-with-yaml-on-IBM-Z-and-IBM-P.md).

		@@ -0,0 +1,35 @@
		Use the following steps to install Istio and set it as the ingress conroller.

		1. Install a properly configured Istio:


		Review the following tabs to determine the optimal networking layer for your cluster. For most users, the Kourier ingress controller is sufficient in conjunction the default Istio gateway, which is also included in the Knative Serving installation. You can expand your capabilities with the Contour ingress, a full-feature service mesh with Istio, and the Kubernetes Gateway API.

		=== "Kourier"

	kubectl apply -f https://github.com/knative/net-kourier/releases/latest/download/kourier.yaml
	kubectl apply -f {{ artifact(org="knative-extensions", repo="net-kourier", file="kourier.yaml" }}


		## Network layer options

		Review the following tabs to determine the optimal networking layer for your cluster. For most users, the Kourier ingress controller is sufficient in conjunction the default Istio gateway, which is also included in the Knative Serving installation. You can expand your capabilities with the Contour ingress, a full-feature service mesh with Istio, and the Kubernetes Gateway API.


		The Kourier ingress controller, `net-kourier`, is installed with Knative Serving. Kourier is a lightweight alternative for the Istio ingress as its deployment consists only of an envoy proxy and a control plane. If Kourier is satisfactory, no further configurations are required.

		Kourier is the only supported ingress controller for the IBM Z and IBM Power platforms, and requires additional steps as documented in [Install Serving with YAML on IBM-Z and IBM-P](/versioned/install/yaml-install/serving/install-serving-with-yaml-on-IBM-Z-and-IBM-P.md).

Create Configure Knative Networking page #6518

Are you sure you want to change the base?

Create Configure Knative Networking page #6518

Uh oh!

Conversation

iRaindrop commented Nov 19, 2025

Proposed Changes

Uh oh!

netlify bot commented Nov 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for knative ready!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

iRaindrop Dec 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Cali0707 commented Dec 1, 2025

Uh oh!

knative-prow bot commented Dec 1, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

evankanderson left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

netlify bot commented Nov 19, 2025 •

edited

Loading

iRaindrop Dec 1, 2025 •

edited

Loading