Hi, there is a bug when you have two ingress controlles with the same host, if you try to separate in two ingress (each ingress for triangule and circule) the nginx-ingress-controller will create two config file ( default-circule.conf and default-triangule.conf) and both config file will have the same host and the nginx dashboard will show warning in server zone. I think the nginx-ingress-controller should create config file per servername and not per deployment. In may case I have Almost 50 deployments and each app has their ingress.yaml with the same host (obviously diferente ports).
nice video, thank you for share, I have a question, I recently heard at a conference that it was a good practice to use multiple ingress controllers in Kubernetes. Why?
Both nginx IC and L7 proxy will be in the same pod, these pods will be replicated by deployment and exposed by the load balancer service type since the service type is Load balancer we need an L3/L4 load balancer provided by a cloud vendor outside the cluster. hope this clarifies.
Unable to access my kube cluster after applying nginx-config.yaml for tcp/udp. I am getting error like Unable to connect to the server: dial tcp: lookup A13E7B443XYZCVBDS7868822.ak1.cp-abcd-5.eks.amazonaws.com on 172.31.0.2:53: no such host
Thanks dude It is good video presentation. I looking for this kind video. Thanks a lot man I got 504 gateway error when try to connect edge server. So i need to update port forwarding and proxy annotations is this correct
Michael, Thaaaaank you, guys like you make the world better place by such contributions, keep it up and running :)
- I will show you now how to do X
- Me: yes, finally
- But before I do that, let us jump back
- No, no, no , not back, no jumping, just show me
Hi, there is a bug when you have two ingress controlles with the same host, if you try to separate in two ingress (each ingress for triangule and circule) the nginx-ingress-controller will create two config file ( default-circule.conf and default-triangule.conf) and both config file will have the same host and the nginx dashboard will show warning in server zone. I think the nginx-ingress-controller should create config file per servername and not per deployment. In may case I have Almost 50 deployments and each app has their ingress.yaml with the same host (obviously diferente ports).
nice video, thank you for share, I have a question, I recently heard at a conference that it was a good practice to use multiple ingress controllers in Kubernetes. Why?
All I need to know about nginx controller. Thanks a lot.
Still not clear about the need for L3/4 load balancer in front of L7 nginx.
Both nginx IC and L7 proxy will be in the same pod, these pods will be replicated by deployment and exposed by the load balancer service type since the service type is Load balancer we need an L3/L4 load balancer provided by a cloud vendor outside the cluster. hope this clarifies.
Great introduction video to nginx ingress. Learned so much. Thanks
Unable to access my kube cluster after applying nginx-config.yaml for tcp/udp. I am getting error like
Unable to connect to the server: dial tcp: lookup A13E7B443XYZCVBDS7868822.ak1.cp-abcd-5.eks.amazonaws.com on 172.31.0.2:53: no such host
so on which port is the ingress controller listening? 80? I did not see that specified anywhere in the ingress resource yml file.
yeah it should be port 80
and 443 for https
HI the video is awesome ....could you pleaes mention the git repo used in the video it will be help fill thanks! cheers.
great content. keep up.
Ngnix ingress cannot fetch the service from different namespace? Any solution for this...
Thank you for this video !!
Thanks dude It is good video presentation. I looking for this kind video. Thanks a lot man
I got 504 gateway error when try to connect edge server. So i need to update port forwarding and proxy annotations is this correct
Nice talk, ty Michael
Great talk. Could you share the helm chart file by any chance?
Great presentation :)
boring should be crisp and clear..
You’re welcome to do it
Lol