How to debug Kubernetes? (Deployments, Services & Ingress)

[@AntonPutra]

🔴 To support my channel, I'd like to offer Mentorship/On-the-Job Support/Consulting ([e-mail])

[@AnanthaRamachandranB]

How are your mentorship programs

[@shivamanand8998]

With just watching the video for 3 minutes, I was able to debug my issue. Thank you, friend.

[@AntonPutra]

my pleasure!

[@2ndx]

Thanks!🔥

[@AntonPutra]

🙌

[@mechwarrior83]

this info is gold! I will be watching this another 100 times

[@AntonPutra]

❤

[@av1654]

This has helped me troubleshoot and resolve issues in our k8 environment. Thank you so much and such an amazing delivery 👍

[@AntonPutra]

thank you!!

[@loknathsingh1080]

One of the best quality content present on KZbin ❤ Your tutorials are very useful

[@AntonPutra]

thank you!

[@bellakhalmohamed3255]

Thanks man been working with k8s 3 years but I learned so much

[@AntonPutra]

❤️

[@binarylife1100]

dope content...senior engineer stuff, Thanks again

[@AntonPutra]

thank you!

[@EdMane]

omg this is pure gold! thank you so much! I would like to ask a few question if I may. I read topologySpreadConstraints is used so our Pods can be spread between AZs evenly. Do I have to declare it inside the kind: Deployment? and If I'm using Karpenter, Does it will deploy a new node on a diferent AZ if the deployment wants another AZ? or does the nodes must exist in all AZs before? thanks!!

[@AntonPutra]

Thanks! Usually, in the cloud when you create Kubernetes, each node will get an additional label with the availability zone, and you can use node affinity along with pod anti-affinity to spread them between AZs. - To find values use "kubectl describe node " - For affinity - kzbin.info/www/bejne/qImXp5KCZdBnfsU

[@Antonio-yy2ec]

Great content as always, Anton!!

[@gurudattshanbhag8878]

Great content! Saviour!

[@AntonPutra]

thank you!

[@maxcoder95]

Awesome content. I know most of the content in the video watched this as a refresger, however i did not know about the curl commands and it made my life easier. It will be really cool if you can create content about Failover scenarios like cluster failover when region failed or multiple cluster microservices communication. I know it is advanced topic but I think it will be helpful.

[@AntonPutra]

thanks, i'll see what i can do

[@sufiyanhabib4431]

Very awesome tutorial!!

[@AntonPutra]

thank you!

[@israel8707]

Excellent video, like always 😊

[@AntonPutra]

❤️

[@gabecerts4286]

Thank you, you are awesome!

[@AntonPutra]

😊

[@ZeroReadHQ]

Gold!

[@AntonPutra]

thank you!

[@chiragcloud]

Excellent explanation and thanks for sharing the valuable info, Can you share how you are creating this slides or which platform your using. its very attractive and I would like to use this method for my customer to explain them the flows and architectures.

[@AntonPutra]

thanks! well, i use adobe suite and spend a lot of time animating...

[@chiragcloud]

@@AntonPutra Great. thanks for sharing and kudos for your efforts.

[@farzadmf]

Very nice video, thank you!

[@AntonPutra]

❤️

[@neelojp8460]

thank you so much @AntonPutra, you explain that in short and very good way! thanks for your time :-) any videos about how we can install Ingress-Nginx :-)) that would be also good

[@AntonPutra]

no problem, here is terraform but you can easily convert it to plain commands, don't forget values - github.com/antonputra/tutorials/blob/108c009be032f53c1cf9139b808da32e826e7783/lessons/177/terraform/7-nginx-ingress.tf#L18-L28 Another video coming soon in 2-3 days, on installation and debugging ingress with tls and cert-manager.

[@ИванБижев-х8б]

Hey @AntonPutra, I see that you're using minikube on mac, but afaik ingress, and ingress-dns addons are currently only supported on Linux as docker is not running in the same manner on mac m series as linux. Did you use a qemu driver or something else entirely?

[@AntonPutra]

No, it’s standard minikube, I didn’t install anything extra.

[@kalathti]

Thank you so much 🙏

[@AntonPutra]

❤️

[@ziad_m_404]

We are waiting for the private ingress nginx video with VPN and the private Rout53 or splitdns ^^ It would be amazing if we included multiple controllers at the same time. Can not thank you enough for your amazing priceless content ^^.

[@AntonPutra]

Thanks, but I already have a VPN setup that includes pushing private Route53 hosted zones to your laptop. The only missing part is ingress, which is converted from public to private by using a single annotation. VPN - github.com/antonputra/tutorials/tree/main/lessons/084 Private ingress - github.com/antonputra/tutorials/blob/108c009be032f53c1cf9139b808da32e826e7783/lessons/149/terraform/11-internal-ingress-nginx.tf#L13

[@ziad_m_404]

@@AntonPutra thanks a TON ^^

[@GabrielPozo]

Thank you!!!! 👏👏👏

[@harishdevarapalli1537]

Thanks sir.!!!

[@AntonPutra]

🙏

[@AntonPutra]

🍿 Benchmarks: kzbin.info/aero/PLiMWaCMwGJXmcDLvMQeORJ-j_jayKaLVn&si=p-UOaVM_6_SFx52H

[@gazizovemil]

Awesome tutorial. Could you please tell about secrets and configs?

[@AntonPutra]

Thank you! Sure soon, i was planning a video k8s secrets vs configmap (best practises)

[@nguyenphu-o5d]

Hi, can I ask how to use nginx ingress if my ingress and my app have different namespaces?

[@AntonPutra]

It's a very rare use case. Are you sure you cannot create an ingress in the same namespace? Can you describe your requirements? There are some workarounds with external services, but it's unlikely that you need that. kubernetes.io/docs/concepts/services-networking/service/#externalname

[@nguyenphu-o5d]

@@AntonPutra Thanks, I will tried configure the deployment, ingress and service file into the same namespace where I deploy my app.

[@AntonPutra]

@@nguyenphu-o5d Just to clarify, for example, you would deploy your application to the 'staging' namespace and deploy the ingress controller to the 'ingress' namespace. This does not mean that your app must be deployed in the 'ingress' namespace. That namespace is only for the controller itself. Instead, you would create an 'Ingress' object in the 'staging' namespace. Ingress object example - github.com/antonputra/tutorials/blob/main/lessons/194/1-example/3-ingress.yaml#L3 On line 5 you would have 'staging' namespace.

[@nguyenphu-o5d]

@@AntonPutra tks, I have figured out the issue, it was between my service and my custom nginx-ingress. Can I use minikube or microk8s with nginx plus?

[@AntonPutra]

@@nguyenphu-o5d well you can just deploy it using helm chart or yaml, don't use "minikube addons enable ingress"

[@AcessHall]

Thank you

[@AntonPutra]

my pleasure!

[@diegonayalazo]

❤

[@AntonPutra]

thanks :)

[@ShourovRoy-pk5zm]

Can you please make a video on mongodb replicaset with authentication and external access from k8s. Please 🙏

[@AntonPutra]

Ok, i think it's time to refresh the previous tutorial

[@ShourovRoy-pk5zm]

​@@AntonPutra thank you for your kind reply. The mongodb auth us working without replicaset of mongodb and replicaset is working without auth. As transaction only supports when mongodb has the following command "--replSet" Didn't get any solution anywhere. Everywhere is helm. But need to learn it using k8s only. Please.

[@AntonPutra]

@@ShourovRoy-pk5zm there should be community k8s operator, have you tried thaty?

[@ShourovRoy-pk5zm]

@@AntonPutra they are using helm. Can't we achieve it using raw k8s ymls.?

[@AntonPutra]

@@ShourovRoy-pk5zm you can, but it'll take me while to create tutorial

[@levu74]

Great video! +1 like +1 subcribe

[@AntonPutra]

cool, thanks!