# This section is only required if TLS is to be enabled for the Ingress You can watch the status by running 'kubectl -namespace default get services -o wide -w washing-jackal-nginx-ingress-controller'Īn example Ingress that makes use of the controller: It may take a few minutes for the LoadBalancer IP to be available. The nginx-ingress controller has been installed. Washing-jackal-nginx-ingress-default-backend-57947f94c6-h4sz6 0/1 ContainerCreating 0 0s Washing-jackal-nginx-ingress-controller-5b4d86c948-xxlrt 0/1 ContainerCreating 0 0s Washing-jackal-nginx-ingress-default-backend 1 1 1 0 0s Washing-jackal-nginx-ingress-controller 1 1 1 0 0s NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE Washing-jackal-nginx-ingress-default-backend ClusterIP 10.103.189.14 80/TCP 1s NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE Washing-jackal-nginx-ingress-controller 1 1s Will this work on localhost - and if so, how to access a service? Installing Ingress using Helm on Docker for Mac(Edge with Kubernetes) My-release-nginx-ingress-default-backend ClusterIP 10.98.230.24 80/TCP 10m I got the NodePort to work: kubectl get services NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |