Skip to content

Update service name for istio gateway

Steve Xuereb requested to merge update-finding-knative-ingress into master

What does this MR do?

Update service name for istio gateway

When installing knative with GitLab managed apps. There is no service named knative-ingressgateway under the istio-system namespace.

For example:

kubectl get svc --all-namespaces 
default                                  kubernetes                        ClusterIP      10.91.0.1      <none>                                                 443/TCP                                      42h
gitlab-managed-apps                      tiller-deploy                     ClusterIP      10.91.7.28     <none>                                                 44134/TCP                                    42h
istio-system                             cluster-local-gateway             ClusterIP      10.91.0.11     <none>                                                 15020/TCP,80/TCP,443/TCP                     42h
istio-system                             istio-ingressgateway              LoadBalancer   10.91.7.193    xx.xx.xx.xx                                           15020:32547/TCP,80:30512/TCP,443:31257/TCP   42h
istio-system                             istio-pilot                       ClusterIP      10.91.3.36     <none>                                                 15010/TCP,15011/TCP,8080/TCP,15014/TCP       42h
istio-system                             istio-telemetry                   ClusterIP      10.91.14.237   <none>                                                 9091/TCP,15004/TCP,15014/TCP,42422/TCP       42h
knative-serving                          activator-service                 ClusterIP      10.91.12.14    <none>                                                 80/TCP,81/TCP,9090/TCP                       42h
knative-serving                          autoscaler                        ClusterIP      10.91.4.250    <none>                                                 8080/TCP,9090/TCP,443/TCP                    42h
knative-serving                          controller                        ClusterIP      10.91.12.79    <none>                                                 9090/TCP                                     42h
knative-serving                          webhook                           ClusterIP      10.91.5.186    <none>                                                 443/TCP                                      42h
kube-system                              default-http-backend              NodePort       10.91.12.176   <none>                                                 80:30907/TCP                                 42h
kube-system                              heapster                          ClusterIP      10.91.4.54     <none>                                                 80/TCP                                       42h
kube-system                              kube-dns                          ClusterIP      10.91.0.10     <none>                                                 53/UDP,53/TCP                                42h
kube-system                              metrics-server                    ClusterIP      10.91.2.41     <none>                                                 443/TCP                                      42h
merge-request-bot-17349153-development   merge-request-bot                 ExternalName   <none>         cluster-local-gateway.istio-system.svc.cluster.local   <none>                                       42h
merge-request-bot-17349153-development   merge-request-bot-2dl9g           ClusterIP      10.91.9.112    <none>                                                 80/TCP                                       42h
merge-request-bot-17349153-development   merge-request-bot-2dl9g-fld8m     ClusterIP      10.91.11.147   <none>                                                 80/TCP,8022/TCP                              42h
merge-request-bot-17349153-development   merge-request-bot-2dl9g-metrics   ClusterIP      10.91.13.117   <none>                                                 9090/TCP,9091/TCP                            42h

Related issues

Author's checklist

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

  • Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

  • Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.

3. Maintainer

  1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  2. Ensure a release milestone is set.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.

Merge request reports