this is the best explanation I've ever seen for Ingress. None of the courses explain so good, thank you!

@DevOpsMadeEasy

8 ай бұрын

Glad it was helpful!

@dhirendrasatyapal977

4 ай бұрын

hi how are you

@NikolaNovoselec

4 ай бұрын

I agree!

much needed video! thanks vikram

Damn !!!, the best session i've ever had in youtube!!!!

@DevOpsMadeEasy

Жыл бұрын

Thanks :)

Nice one.

best explanation I have heard! thank you

@DevOpsMadeEasy

Жыл бұрын

Thanks

This was the best tech session I've seen on KZread. I'll check a few more videos and if the quality is similar I'll definitely join Premium.

@DevOpsMadeEasy

4 ай бұрын

Thanks

Maza aa gya

Hence you Proved the name of yr channel Devops made easy you made ingress concept easy

@DevOpsMadeEasy

Жыл бұрын

Thank you :)

the best ingress video i have seen till now on youtube. Thankyou sir.

@DevOpsMadeEasy

Жыл бұрын

You are welcome :)

Awesome explanation 👏

@DevOpsMadeEasy

Жыл бұрын

Thanks

Hi, Great explanation. Where can we find the code for all these.

Hello Sir, thanks for the video with clear explanations. Please, where can I find the code files used in the video? Your prompt response will be appreciated. Thanks.

Please make in depth video on argocd and if possible series on red hat open shift on aws

Can you please make a video on Production ready EKS Cluster provisioning

please can i get the slides? this is truly woooooooooooow. Thank you

Thank you a lot! I really appreciate your lessons. How I can support you?

@DevOpsMadeEasy

Жыл бұрын

You are welcome! You can support through memberships :)

❤

dear how to check the communication between the pods in two clusters ?? there is a dnsname:9092 in which i can check the connection between a pod in one cluster and dnsname:9092 of another cluster? the thing is i don`t have the curl from the pod cluster and from the dnsname:9092 cluster i do have access to execute curl commands, how to check the connectivity between these to its [kafka to some pod running in other cluster] could you kindly please reply ?

Can you let me know do you have any playlist for kubernetes in order ?

@DevOpsMadeEasy

2 жыл бұрын

Yes it is ij order

sir if we edit the /etc/hosts file of ec2 instance on aws will it work as u showed in this video for domain names ?

@DevOpsMadeEasy

Жыл бұрын

yes it will

hi sir, i have a doubt. in ingress path based routing /details, the application in flask-details container is running on / or /details? is there any rule that the app also should run on that particular given path??

What was that middleware in between pod and service. What actual it does?

@DevOpsMadeEasy

Жыл бұрын

Refer to my video on Kubernetes services for this

@pjj7466

Жыл бұрын

@@DevOpsMadeEasy Please share the link. there any multiple videos in channel.

i need kubernetes full course, can you provide me details

Hello Sir, I have replicated the exact same architecture for path based routing using AKS on Azure and ngnix controller. But when I try to access the application from browser,it keeps giving 404 error page of ngnix. I just cannot figure out why it's not working. Can you please help

@premierde

Жыл бұрын

Were you able to figure out why ingress nginx thows 404

@premierde

Жыл бұрын

Verify the path in ing & how have you set rewrite -target.

Confused-If we have an on-prem cluster with 10 nodes and we have 1 nginx-ingress-controller, do we need an additional load balancer to route requests across nodes OR its not needed because the balancing is done by the services (which have already deployed pods of our app on multiple nodes)?

@meghrajraee873

3 ай бұрын

I think you don't need to have any additional load-balancer to route requests across nodes, regardless of the number of nodes in the cluster. If your application is not configured with `NodePort` (the de facto use case of ingress controller but you can have one), then the nginx ingress controller is responsible for directing the request to the associated application service, ultimately ending to the application pod. Unlike, loadbalancer which directs the requests to the corresponding service object, where the service load-balance the request to the pod. nginx ingress controller directs the request directly to the corresponding pods instead of just directing to the associated application service and leaving the service to load-balance to its associated pods. Hope, this will help you.

Hi. At 22:45 you are not refering to request http headers. That info is only for display purpose. Http req headers are in the below block. Please correct me in case i mwrong

@DevOpsMadeEasy

Жыл бұрын

Yes you are true but that displayed info is also correct

@3890mohit

Жыл бұрын

At 1:05:45, u have used cluster ip instead of the ip shown in the kubectl get svc command for nginx service? Cant i access using the nginx service ip?

@DevOpsMadeEasy

Жыл бұрын

Yes

@DevOpsMadeEasy

Жыл бұрын

@@3890mohit ClusterIPs are internal to the cluster. I have used my minikube cluster's IP address and Port on which my Nginx service is exposed as NodePort

link plz

Explanation is good, but u kept different different membership levels for different different topics, initially i gone through gold but few videos only I can access for remaining videos it is asking platinum, palladium membership this is not good,this is advantage for you not for us.

@DevOpsMadeEasy

Жыл бұрын

This is old series. Already we have created a new one

apache virtual hosting is ingress only

i took two months membership im not able to watch a single video can u say what should i do ?

@DevOpsMadeEasy

Жыл бұрын

Which membership?

@nohandsignal

Жыл бұрын

@@DevOpsMadeEasy platinum

@DevOpsMadeEasy

Жыл бұрын

Palladium is required for k8s

It does not get redirected, throws 404. ? what is rewrite-target. If cotext-path is set in springboot, It won't work. Why?

@DevOpsMadeEasy

Жыл бұрын

Rewrite target is changing context. If I access ingress controller on the path /signin, it will also use the same path at the app level but assume your app has /login instead of /signin, this is where you change the path which is redirection

@DevOpsMadeEasy

Жыл бұрын

Lets assume you access the ingress controller on path /api/v1 and your app only support /v1 endpoint, we strip off the /api from the request before sending to the app. This is called rewrite target