Best course on Udemy for Kubernetes and AWS. Really a zero to hero type. Request you to either add or create a separate course for helm charts. And use of them in CI-CD pipeline.
Thanks Deepak! I'll look into that although I'm not a heavy user of helm charts personally. I've also got a pretty urgent job to get the existing course updated with Helm 3, it's been languishing on my TODO list for months now!
This is a great video. I was able to get it to work thanks to your instructions here. Please don't take this video down. Great course of yours by the way. I'm almost finished with it!!
Thank you Richard, very useful and interesting addon to your great AWS course! One of the best out there. Looking forward to starting your Istio course on K8s.
I have a cluster with an external-dns controller and aws-load-balencer controller. Just a few days ago, they added a group feature to where the load balencer controller creates a single ALB in AWS with a target group per Ingress object in the cluster. This all seems to work with our plans of having about 10 different (related) web sites in the cluster. However, we now may want to add Istio. I bought your course on Udemy to understand what I need to do to bring Istio to this cluster. However, the gateway is where I'm stuck because the aws-load-balencer controller wants to route traffic directly to the app pods instead of through the gateway. If I use the method in this video, I beleve that it uses a classic load balencer, and I was hoping to use an application load balencer because we have a few things outside of the cluster as well. I guess that I could proxy it through an Nginx pod in the cluster, which has the nice side effect of that traffic being monitored by Istio. Is there any reason that I should be concered about moving an ALB app to a CLB? The Ingress objects probably won't work as they are because the aws load balencer controller and external dns controller probably both need to be removed to make the gateway work.
Thank you for this tutorial. While it explained the overall concepts, I was unable to follow the steps as the process has changed. Do you have a more recent tutorial anywhere? I also just purchased your Istio course. Is ingress compatible with Istio? If we start using Istio, do we still need Ingress?
Oh dear, sorry about this - it's a while since I last reviewed this video, what has changed in the process? Re Istio - pretty much you don't need Ingress with Istio because it has it's own version of Ingress (the gateway). It 90% replaces the functions of that. The process of setting up TLS for Istio is the same as here (terminating at the load balancer) - if it works that is! Report back!
@@RichardChesterwood I figured it out, all sorted. Thank you! Re: What changed? The installation instructions for the Nginx Ingress controller. There are two methods on the official website. The first creates a network load balancer, the second (which creates an elb) requires some updates to the manifest before applying. I went with the NLB and handled TLS termination within the cluster using cert-manager. Your videos were very helpful. I can't wait to get started with Istio. Thank you, Richard!
Thanks this great video, it helps me a lot. And I have a question: Could you tell me if i want to handle multi host and also TLS terminate at ELB, how to implement it? Should I have multiple ingress controller and multiple ELB?
Thanks! I would use an Ingress controller yes - but you don't need multiple ELBs in that case. I would use subdomains if possible like host1.mydomain.com, host2.mydomain.com, etc. Point each of these domains at the ELB, and the ingress controller will be able to forward to the correct service using the subdomain name.
@@RichardChesterwood Thank you for your reply, and sorry that I did not describe clearly. I need to handle different root domain just like foo.bar1.com, foo.bar2.com, foo.bar3.com..... It seems like i have to create a separate elb for each root domain name.
@@wangzhipeng4585 I can't see a problem with creating a DNS record for each of your domains, with each of them pointing to the same ELB. Then use the ingress controller to route the traffic. I might have missed something though, I'm writing this after a LONG recording session and I could probably happily tell someone that the sun definitely orbits the moon. Or something ;-)
Best course on Udemy for Kubernetes and AWS. Really a zero to hero type.
Request you to either add or create a separate course for helm charts. And use of them in CI-CD pipeline.
Thanks Deepak! I'll look into that although I'm not a heavy user of helm charts personally. I've also got a pretty urgent job to get the existing course updated with Helm 3, it's been languishing on my TODO list for months now!
Great course Richard. You explained clearly all topics.
Many thanks! Quite an old video this one, glad that there's still some value in it! All the best!
Best Course for Kubernetes ever, I watched a lot of courses but this course is the one
Many thanks! Always a relief to hear the course is useful! All the best!
Marvelous job Richard! What a video! I also have bought multiple courses of yours on Udemy. Well done mate!
Many thanks Rocky! I'm desperate to make new courses but so much to do! All the best!
This is a great video. I was able to get it to work thanks to your instructions here. Please don't take this video down. Great course of yours by the way. I'm almost finished with it!!
Many thanks!
Thanks a lot Richard. Lots of love from India
Many thanks and love returned from the UK! All the best!
Thank you Richard, very useful and interesting addon to your great AWS course! One of the best out there. Looking forward to starting your Istio course on K8s.
Many thanks Petr! Hope the Istio course goes well for you!
thanks for the great udemy course mate!
Ah many thanks, you're very kind!
Awesome course! I continued from your online course in udemy.
Ah that's great Muthu! Great to see you here!
I have a cluster with an external-dns controller and aws-load-balencer controller. Just a few days ago, they added a group feature to where the load balencer controller creates a single ALB in AWS with a target group per Ingress object in the cluster. This all seems to work with our plans of having about 10 different (related) web sites in the cluster. However, we now may want to add Istio. I bought your course on Udemy to understand what I need to do to bring Istio to this cluster. However, the gateway is where I'm stuck because the aws-load-balencer controller wants to route traffic directly to the app pods instead of through the gateway. If I use the method in this video, I beleve that it uses a classic load balencer, and I was hoping to use an application load balencer because we have a few things outside of the cluster as well. I guess that I could proxy it through an Nginx pod in the cluster, which has the nice side effect of that traffic being monitored by Istio. Is there any reason that I should be concered about moving an ALB app to a CLB? The Ingress objects probably won't work as they are because the aws load balencer controller and external dns controller probably both need to be removed to make the gateway work.
Thanks for the video! It is very usefull.
Thanks Ivan!
Thank you for this tutorial. While it explained the overall concepts, I was unable to follow the steps as the process has changed. Do you have a more recent tutorial anywhere? I also just purchased your Istio course. Is ingress compatible with Istio? If we start using Istio, do we still need Ingress?
Oh dear, sorry about this - it's a while since I last reviewed this video, what has changed in the process? Re Istio - pretty much you don't need Ingress with Istio because it has it's own version of Ingress (the gateway). It 90% replaces the functions of that. The process of setting up TLS for Istio is the same as here (terminating at the load balancer) - if it works that is! Report back!
@@RichardChesterwood I figured it out, all sorted. Thank you! Re: What changed? The installation instructions for the Nginx Ingress controller. There are two methods on the official website. The first creates a network load balancer, the second (which creates an elb) requires some updates to the manifest before applying. I went with the NLB and handled TLS termination within the cluster using cert-manager. Your videos were very helpful. I can't wait to get started with Istio. Thank you, Richard!
Thanks this great video, it helps me a lot. And I have a question: Could you tell me if i want to handle multi host and also TLS terminate at ELB, how to implement it? Should I have multiple ingress controller and multiple ELB?
Thanks! I would use an Ingress controller yes - but you don't need multiple ELBs in that case. I would use subdomains if possible like host1.mydomain.com, host2.mydomain.com, etc. Point each of these domains at the ELB, and the ingress controller will be able to forward to the correct service using the subdomain name.
@@RichardChesterwood Thank you for your reply, and sorry that I did not describe clearly. I need to handle different root domain just like foo.bar1.com, foo.bar2.com, foo.bar3.com..... It seems like i have to create a separate elb for each root domain name.
@@wangzhipeng4585 I can't see a problem with creating a DNS record for each of your domains, with each of them pointing to the same ELB. Then use the ingress controller to route the traffic. I might have missed something though, I'm writing this after a LONG recording session and I could probably happily tell someone that the sun definitely orbits the moon. Or something ;-)
too small font. I can't read terminal.
Doh sorry about that. I hope it plays out better on Udemy than here. Hope that maybe there was something in there of use at least. All the best.
@@RichardChesterwood font size is good, if its too small your monitor is too small lol