Kubernetes Ingress: NGINX Explained

In this episode, we take a look at the NGINX Kubernetes Ingress controller.
We'll cover what an ingress controller is, what an ingress is, all the features and finally a hands-on example with deployment. All the source code is available on GitHub, check links below.

Also if you want to support the channel further, become a member 😎

Checkout "That DevOps Community" too

If you're interested in learning more about Kubernetes, checkout my series below:

Kubernetes Development Guide:

Kubernetes Monitoring Guide:

Kubernetes Secret Management Guide:

Like and Subscribe for more :)

Source Code

Follow me on socials!

Music:

[hayesroach]

love your energy and your passion for kubernetes!

[svendavison]

Watched over 16 hours of videos reguarding K8s. I got what i needed in this 14 1/2 minute video. Still a few lingering questions but this helped a lot.

[umermustafa]

I really love the way you present the content ... hats off to you.

[cellwall]

Thank you again for your videos. I assume like many Software Engineers, I have bought several udemy etc classes and books. However none have made me understand Kubernetes and DevOps tools like your videos. I just started a new position, and if you are accepting ideas for topics to cover, I'd like to see more topics on the following tools: GitOPs pipelines
, Rancher, Fleet, Argo, security for containers and Pods, lastly Hashi products (TerraForm, Packer, and vault). I hope one or two of these entirely selfish ideas, inspire you.

[felipeozoski]

Hands down the BEST tutorials on YouTube!!! Take my money!!!

[rougearlequin]

I am only 2 minutes into the video, and I already gave thumbs up. It shows you put some time into preparing it!

[dharanidaranaladiyurparama]

Thanks a lot for this quick and informative tutorial

[TythosEternal]

I thought I had started to wrap my head around services and namespaces but then I got to the 5:00 mark and now I'm confused why you need entirely different instances of these resources for a single ingress; seems like it's mainly to isolate networking control permissions within a separate service and namespace? So I asked ChatGPT:

"Applying the ingress controller under a separate namespace and service from the rest of the deployment in Kubernetes offers several benefits:

Isolation and Segregation: By placing the ingress controller in its own namespace, you create a logical separation between the ingress controller and the other components of your application. This isolation helps in managing and securing the ingress controller independently. It also prevents accidental modifications or interference from other components.

Security and Access Control: Placing the ingress controller in a separate namespace allows you to apply different security policies and access controls specifically for the ingress controller. You can define granular RBAC (Role-Based Access Control) rules to restrict access to the ingress controller's resources, making it more secure and minimizing the risk of unauthorized access.

Scalability and Resource Management: Ingress controllers often handle a large amount of incoming traffic and routing rules. By isolating the ingress controller in its own namespace, you can assign dedicated resources (CPU, memory) to it and manage its scaling separately from other application components. This ensures that the ingress controller has sufficient resources to handle the ingress traffic effectively without impacting other parts of the system.

Ease of Maintenance and Upgrades: Separating the ingress controller into its own namespace simplifies maintenance tasks. You can upgrade or roll back the ingress controller independently of other components, reducing the impact on the overall application. It also allows you to monitor and troubleshoot the ingress controller more effectively since its logs and metrics are contained within a dedicated namespace.

Organizational and Operational Clarity: Grouping related components together in separate namespaces promotes better organization and clarity within your Kubernetes cluster. It helps distinguish between infrastructure-related components (like ingress controllers) and application-specific components, making it easier for team members to understand and manage the system.

Overall, applying the ingress controller under a separate namespace and service enhances security, isolation, scalability, and maintainability of the ingress infrastructure, enabling better management and control over traffic routing in Kubernetes deployments."

Isn't technology amazing?

[teamsre]

Thank you for the video.
While turning away from main camera might create a dynamic setting for tutorial, the audio quality significantly drops every time you so, making the sound uneven.

[bhoopeshdevops]

You are a gem 💎.. Treat to watch your vedios

[navneet]

This devops guy is awesome keep making videos like this

[Itsme-kxus]

Sir u r like God🙏🙏🙏🙏🙏
Such an amazing content sir
Tq soooo much

[jayhawkelectrical]

Marcel, you are the man. Fantastic video! Thank you.

[obe]

this was amazing please make a video about Gatekeeper

[aquual]

Great vid, quick, good explanation and provided source files, The transition between code and side cam are also really nice.

[DominicBurford]

Great content, you have a new subscriber.

[JackLogan]

Amazing video! Thanks for the good lesson and the quality content!

[paracha]

I was hoping to bypass the Cloud Provider LB service (too expensive) and expose my service in cloud to the internet. Unfortunately many tutorials like this one only show local k8s setups which are fairly easy and does not reflect real world cloud provider k8s challenges. Hope you will cover that in future video.

[StringsAcrossBorders]

Hi Marcel. Your videos are really awesome and I'm learning a lot of new things from them which has actually helped me in my professional career. I really appreciate your efforts in making the content for us!

I had a query regarding the ingress and ingress controller mapping. Let's say I have 3 different nginx ingress controllers in my cluster and I want to use a specific ingress controller for a specific ingress. How do I define which exact controller to use for an ingress. I know it is done using class annotation or "ingressClassName" attribute under the ingress spec section but which value goes there to identify the ingress controller. I didn't found much info on this on the internet (maybe I'm not looking at the right direction)

[ayeleru]

Awesome video! intro was especially good. only thing that needs a bit of an improvement is the audio volume