Create Configure Network Adapters page #6518
Conversation
Create file - table test
✅ Deploy Preview for knative ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
knative-prow
bot
added
the
size/S
knative-prow
bot
added
the
do-not-merge/work-in-progress
Formatting test
More writing
knative-prow
bot
added
size/M
Snippet testing
snippet testing
Snippet name fix
Formatting tests
Formatting fix
Formmating
Typo fix
Formatting
knative-prow
bot
added
size/L
Updates
Snippet formatting
Misc edits
Link issue fix
Minor edit to rebuild
Formatting fix
Consistency edits
Format fix
Refinement edits
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
|
|
||
| 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). |
There was a problem hiding this comment.
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.
| 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). |
There was a problem hiding this comment.
Decision to make - bring the topic into this tab or not?
| @@ -0,0 +1,35 @@ | |||
| Use the following steps to install Istio and set it as the ingress conroller. | |||
|
|
|||
| 1. Install a properly configured Istio: | |||
There was a problem hiding this comment.
The artifact "macros" are not rendering to provide the URL. I wasn't able to find this one.
| kubectl apply -f {{ artifact(repo="net-istio",file="net-istio.yaml")}} | ||
| ``` | ||
|
|
||
| <!-- 1. Set the `config-network` ConfigMap to use Istio: |
There was a problem hiding this comment.
I added this ConfigMap patch step that might not be correct. Or does Istio make the ingress controller connection without the ConfigMap?
knative-prow
bot
removed
the
do-not-merge/work-in-progress
|
/assign @dprotaso @evankanderson |
Updated Gateway API steps
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: iRaindrop The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
| 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: |
There was a problem hiding this comment.
Is channel the right word? Doesn't the ConfigMap need to configure the underlying ingress controller?
Fixed typos and tweaking
Minor edit to rebuild
Consistency edits
|
|
||
| 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" |
There was a problem hiding this comment.
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!
4 participants
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