search for a certain type of objects (ingress,"nginx") in a clusterĢ. In general, Ingress controller works as follows:ġ. It seems that your cluster is missing Ingress controller. reverse engineering on ingress in kubernetes.It was a long journey to make ingress working on bear metal like environment.Thus, i will include relevant links that helped me along. Stilton-cheese-5f6bbdd7dd-8s8bf 1/1 Running 0 110mįinally, test that request to propagates via ingress load balancer. $ kubectl get podsĬheddar-cheese-6f94c9dbfd-cll4z 1/1 Running 0 110mĮchoserver-55dcfbf8c6-dwl6s 1/1 Running 0 104m Successful, execution of all steps will create ingress controler resource that should look like this. Test that ingress controller is working by executing steps in this tutorial -of course, you will omit minikube part. Don't forget to change pod name! $ kubectl exec -it nginx-ingress-controller-5cd796c58c-lg6d4 -n ingress-nginx - /nginx-ingress-controller -version Ingress-nginx nginx-ingress-controller-5cd796c58c-lg6d4 1/1 Running 0 75mįinally, check ingress controller version. NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGEĬheck that nginx-ingress pod is running. $ kubectl apply -f svc-ingress-nginx-lb.yamlĬheck that ingress-nginx service was created. I do it by downloading NodePort template service from installation tutorial and making following adjustments in svc-ingress-nginx-lb.yaml file. $ kubectl get nodes -o wideįurther, crate ingress-nginx service of type LoadBalancer. Go to installation instructions and execute first step # prerequisite-generic-deployment-command Currently there are two ingress controller worth trying kubernetes nginx ingress controller and nginx kubernetes ingress controller -I installed first one. Here is link to my kubernetes vlab.įirst of all make sure that you have ingress controller installed. I had the same issue on my bare metal installation - or rather something close to that (kubernetes virtual cluster - set of virtual machines connected via Host-Only-Adapter). Is there something I have missed in my configs ? Now when I try accessing the Pods using the NodeIP address (172.16.16.2), I get nothing. This yields : kubernetes]# kubectl describe ing fanout-nginx-ingressĭefault backend: default-http-backend:80 () So my Ingress file is : apiVersion: extensions/v1beta1 Now on top of this I want to deploy an Ingress so that I can reach both pods not using 2 IPs and 2 different ports BUT 1 IP address with different paths. My NodeIP address is 172.16.16.2 and I can access both pods using & My svc are : kubernetes]# kubectl get svc Kubectl expose deployment echoserver -target-port=8080 -type=NodePort I have also created their corresponding services : kubectl expose deployment nginx -target-port=80 -type=NodePort Kubectl run echoserver -image=gcr.io/google_containers/echoserver:1.4 -port=8080 I have created 2 deployments : kubectl run nginx -image=nginx -port=80 I am new to Kubernetes Ingress and am setting up 2 different services, each reachable with its own path. K8S version : 1.9.5 (deployed using KubeSpray)
0 kommentar(er)
