Your video didn't deal with ingress per say. you only addressed load balancer and NodePort as a gateway for the pods to be exposed externally. I was expecting to watch how ingress, ingress control manager and ingress rules are configured for the same purpose.
great tutorial, just a quick question, at 16:49 i expect to access auth pod from book pod should go over cluster ip via kube proxy, not over nodePort and external load balancer bcs Cluster Ip service is internal cluster network and can have access to another pod in another node directly via kube-proxy
Kubernetes Ingress Explained with Hands-On- Demo!
➜ Join our Community Discord: discord.gg/CqeubBfa9t
➜ Follow us on Twitter: @Alta3Research
Your video didn't deal with ingress per say. you only addressed load balancer and NodePort as a gateway for the pods to be exposed externally. I was expecting to watch how ingress, ingress control manager and ingress rules are configured for the same purpose.
Having 3 containers via the number of replicas in a deployment is a replica set ?
great tutorial, just a quick question, at 16:49 i expect to access auth pod from book pod should go over cluster ip via kube proxy, not over nodePort and external load balancer bcs Cluster Ip service is internal cluster network and can have access to another pod in another node directly via kube-proxy
Does the External Load Balancer need to see the Worker nodes or is it enough that the LB is just connected to the masters and vice versa?