mirror of https://github.com/knative/docs.git
Remote references to obsolete knative-ingressgateway. (#2333)
This commit is contained in:
parent
04ea875ab1
commit
35154a5fe5
|
@ -98,9 +98,6 @@ To check the IP address of your Ingress, use
|
||||||
kubectl get svc -n istio-system istio-ingressgateway
|
kubectl get svc -n istio-system istio-ingressgateway
|
||||||
```
|
```
|
||||||
|
|
||||||
Or replace that with `knative-ingressgateway` if you are using Knative release
|
|
||||||
older than 0.3.
|
|
||||||
|
|
||||||
If there is no external IP address, use
|
If there is no external IP address, use
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
|
|
|
@ -33,8 +33,6 @@ spec:
|
||||||
# in order to redirect requests to Search service.
|
# in order to redirect requests to Search service.
|
||||||
authority: search-service.default.example.com
|
authority: search-service.default.example.com
|
||||||
route:
|
route:
|
||||||
# knative-ingressgateway is the k8s service created by Knative as the
|
|
||||||
# shared gateway of all traffic incoming to the cluster.
|
|
||||||
# Basically here we redirect the request to the cluster entry again with
|
# Basically here we redirect the request to the cluster entry again with
|
||||||
# updated header "search-service.default.example.com" so the request will
|
# updated header "search-service.default.example.com" so the request will
|
||||||
# eventually be directed to Search service.
|
# eventually be directed to Search service.
|
||||||
|
|
|
@ -378,7 +378,7 @@ kubectl edit svc $INGRESSGATEWAY --namespace istio-system
|
||||||
```
|
```
|
||||||
|
|
||||||
This command opens your default text editor and allows you to add the annotation
|
This command opens your default text editor and allows you to add the annotation
|
||||||
to `knative-ingressgateway` service. After you've added your annotation, your
|
to `istio-ingressgateway` service. After you've added your annotation, your
|
||||||
file may look similar to this (assuming your custom domain is
|
file may look similar to this (assuming your custom domain is
|
||||||
`external-dns-test.my-org.do`):
|
`external-dns-test.my-org.do`):
|
||||||
|
|
||||||
|
@ -405,7 +405,7 @@ You should see output similar to:
|
||||||
```
|
```
|
||||||
NAME TYPE TTL DATA
|
NAME TYPE TTL DATA
|
||||||
*.external-dns-test.my-org.do. A 300 35.231.248.30
|
*.external-dns-test.my-org.do. A 300 35.231.248.30
|
||||||
*.external-dns-test.my-org.do. TXT 300 "heritage=external-dns,external-dns/owner=my-identifier,external-dns/resource=service/istio-system/knative-ingressgateway"
|
*.external-dns-test.my-org.do. TXT 300 "heritage=external-dns,external-dns/owner=my-identifier,external-dns/resource=service/istio-system/istio-ingressgateway"
|
||||||
```
|
```
|
||||||
|
|
||||||
### Verify domain has been published
|
### Verify domain has been published
|
||||||
|
|
Loading…
Reference in New Issue