knative
/
docs
mirror of https://github.com/knative/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Make kourier first network layer (#4657)

This commit is contained in:
Samia Nneji 2022-01-20 21:09:35 +00:00 committed by GitHub
parent 4ae2a17049
commit 7756bafd58
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 42 additions and 41 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

83
docs/install/operator/knative-with-operators.md
View File

@ -213,13 +213,53 @@ layer to the CR, and configure DNS.
### Install the networking layer ### Install the networking layer
Knative Operator can configure Knative Serving component with different network layer options. Knative Operator can configure the Knative Serving component with different network layer options.
Istio is the default network layer if the ingress is not specified in the Istio is the default network layer if the ingress is not specified in the
Knative Serving CR. Knative Serving CR. If you choose to use the default Istio network layer, you must install Istio on your cluster.
Because of this, you might find it easier to configure Kourier as your networking layer.
Click on each of the following tabs to see how you can configure Click on each of the following tabs to see how you can configure
Knative Serving with different ingresses: Knative Serving with different ingresses:
=== "Kourier (Choose this if you are not sure)"
The following steps install Kourier and enable its Knative integration:
1. To configure Knative Serving to use Kourier, add `spec.ingress.kourier` and
`spec.config.network` to your Serving CR YAML file as follows:
```yaml
apiVersion: operator.knative.dev/v1alpha1
kind: KnativeServing
metadata:
name: knative-serving
namespace: knative-serving
spec:
# ...
ingress:
kourier:
enabled: true
config:
network:
ingress-class: "kourier.ingress.networking.knative.dev"
```
1. Apply the YAML file for your Serving CR by running the command:
```bash
kubectl apply -f <filename>.yaml
```
Where `<filename>` is the name of your Serving CR file.
1. Fetch the External IP or CNAME by running the command:
```bash
kubectl --namespace knative-serving get service kourier
```
Save this for configuring DNS later.
=== "Istio (default)" === "Istio (default)"
The following steps install Istio to enable its Knative integration: The following steps install Istio to enable its Knative integration:
@ -263,45 +303,6 @@ Knative Serving with different ingresses:
Save this for configuring DNS later. Save this for configuring DNS later.
=== "Kourier"
The following steps install Kourier and enable its Knative integration:
1. To configure Knative Serving to use Kourier, add `spec.ingress.kourier` and
`spec.config.network` to your Serving CR YAML file as follows:
```yaml
apiVersion: operator.knative.dev/v1alpha1
kind: KnativeServing
metadata:
name: knative-serving
namespace: knative-serving
spec:
# ...
ingress:
kourier:
enabled: true
config:
network:
ingress-class: "kourier.ingress.networking.knative.dev"
```
1. Apply the YAML file for your Serving CR by running the command:
```bash
kubectl apply -f <filename>.yaml
```
Where `<filename>` is the name of your Serving CR file.
1. Fetch the External IP or CNAME by running the command:
```bash
kubectl --namespace knative-serving get service kourier
```
Save this for configuring DNS later.
=== "Ambassador" === "Ambassador"
The following steps install Ambassador and enable its Knative integration: The following steps install Ambassador and enable its Knative integration: