diff --git a/ee/ucp/kubernetes/layer-7-routing.md b/ee/ucp/kubernetes/layer-7-routing.md index 225f0f6e80..6f68454a81 100644 --- a/ee/ucp/kubernetes/layer-7-routing.md +++ b/ee/ucp/kubernetes/layer-7-routing.md @@ -26,28 +26,3 @@ A popular ingress controller within the Kubernetes Community is the [NGINX contr Learn about [ingress in Kubernetes](https://v1-11.docs.kubernetes.io/docs/concepts/services-networking/ingress/). For an example of a YAML NGINX kube ingress deployment, refer to . -Note that this example uses hostPorts for controller ports. This exposes the host port ( selected in a high range using `hostPort: 38080`) directly into the nodes. -Port 38080 is used for HTTP and port 38443 is used for HTTPS. Make sure that your loadbalancer forwards to the applicable ports on the nodes. You can change them as needed. - -Learn more about [ingress in Kubernetes](https://v1-11.docs.kubernetes.io/docs/concepts/services-networking/ingress/). - -Deploy your controller using `kubectl` and verify pods are deployed successfully: - -``` -🐳 → kubectl apply -f nginx-ingress-deployment.yaml -deployment.extensions "default-http-backend" created -service "default-http-backend" created -configmap "nginx-configuration" created -configmap "tcp-services" created -configmap "udp-services" created -deployment.extensions "nginx-ingress-controller" created - - 🐳 → kubectl get pod -n infra -o wide -NAME READY STATUS RESTARTS AGE IP NODE -default-http-backend-7ff9774865-hsj46 1/1 Running 0 1m 192.168.145.6 dockeree-worker-linux-1 -default-http-backend-7ff9774865-kcqhj 1/1 Running 0 1m 192.168.116.145 dockeree-worker-linux-3 -default-http-backend-7ff9774865-xq566 1/1 Running 0 1m 192.168.247.210 dockeree-worker-linux-2 -nginx-ingress-controller-6b987cbbc6-4qqz8 1/1 Running 0 1m 192.168.145.7 dockeree-worker-linux-1 -nginx-ingress-controller-6b987cbbc6-h6rmg 1/1 Running 0 1m 192.168.116.146 dockeree-worker-linux-3 -nginx-ingress-controller-6b987cbbc6-hkw86 1/1 Running 0 1m 192.168.247.211 dockeree-worker-linux-2 -```