I truly liked your rotating entry in this video. nice setup 😍

I really like the diagrams Viktor! Always helps us visual learners 🙂

Your studio is absolutely awesome man, you gave me some ideas here :)

Your videos help me a lot, thanks! 😊

Love Viktor contents awesome video very good explanation

good explanation thank you

As always great video :)

This Channel is absolutely awesome 😃

You are awesome!

The best channel ever :)

Connecting the LB to suitable available pods is half the battle in production. The other half is security, and I would love to see your take on that!

@DevOpsToolkit

Жыл бұрын

I'm working on something along those lines right now. It should go live in 3 weeks (approx.).

it would have been great if you touched the point of what happens when you are not inside a service provider, but simply installing ingress locally on a cluster. There are still people on my team that don't get what a service of type LoadBalancer is vs a real LoadBalancer.

@DevOpsToolkit

Жыл бұрын

Ingress controllers can handle external LBs in on-prem as well. Nevertheless, that is not that common and, in those cases, one would end up with ports exposed on nodes so that he/she would configure an LB manually. The trick is that Service type LoadBalancer is an extension of Service of type NodePort (which is a way to expose a port). You're right though. I should have covered that scenario in the video. My bad.

@57skies

Жыл бұрын

Ah, don't worry too much! It was supposed to be a minor note only. The video is great, as usual. As a side-note, having ingress controllers "on-prem" is quite the norm in the integration tests world. For example for tests we spin a k3s that comes with traefik with a Service with type LoadBalancer that already exposes port 80, so all we have to do is add proper rules. I hope I make sense here.

@DevOpsToolkit

Жыл бұрын

Having ingress on prem is certainly a norm. I was referring to ingress service being load balancer type and creating external load balancers.

If I deploy an app and I expose the app using NodePort and I put all the k8s ips:port in a load balancer, it works right? What are the disadvantages?

@DevOpsToolkit

Жыл бұрын

The disadvantage is that you're doing extra work. That is, more or less, what ingress does continuously. Apart from extra work, you need to make sure that the list of IPs is always up to date with the nodes you'll add or remove.

Do you have any resources with a high level overview of popular Ingress controllers and their use cases & their pros/cons? Ex: Istio vs NGINX vs Traefik .. etc. Great video btw!

@DevOpsToolkit

Жыл бұрын

That's coming soon. This wednesday we are starting a new series that will include all CNCF projects with comparisons and implementations split into categories. Take a look at the intro (kzread.info/dash/bejne/fJqMy8aIiMSdcdY.html) and stay tuned for the First episode coming in a few days (live stream this wednesday).

Hello, I go through many of the documentation but didn’t find effective way how to install or setup multiple ingress controller in single kubernetes cluster ?

@DevOpsToolkit

Жыл бұрын

Before answering that question, I'd like to understand your use case. Why do you need multiple ingress controllers and should they be of the same or different classes?

@sauravkalal1037

Жыл бұрын

@@DevOpsToolkit the ans is, I’ve frontend and backend in same cluster I wanted to expose services to the ingress but the problem is I wanted them with separate ingress controller so that the load balancer ip will be distinct for frontend and backend ingress controller

@DevOpsToolkit

Жыл бұрын

You can use different ingress controllers or the same controller installed twice with different class names. From there on, you will have to use specific class name in your ingress definitions.

@sauravkalal1037

Жыл бұрын

@@DevOpsToolkit but I want separate load balancer ip to use them ? After using different classes will it provide me the 2 load balancer ip

@DevOpsToolkit

Жыл бұрын

Yes. Each ingress controllers creates a Service of type Load balancer. It's the service that create external lb.