How to Set Up Ingress for Your Kubernetes Services with Traefik or NGINX

Описание: Learn how to efficiently route traffic to multiple services in your Kubernetes cluster using Ingress, Traefik, or NGINX, stripping request prefixes for seamless access.
---
This video is based on the question https://stackoverflow.com/q/75738414/ asked by the user 'IndyStef' ( https://stackoverflow.com/u/6744675/ ) and on the answer https://stackoverflow.com/a/75750249/ provided by the user 'IndyStef' ( https://stackoverflow.com/u/6744675/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Kubernetes newby question on ingress and reverse proxy

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
A Guide to Setting Up Ingress in Kubernetes with Traefik or NGINX

In the age of containerization and microservices, managing multiple applications effectively can be a challenge, especially when migrating from a traditional virtualization setup to a Kubernetes cluster. For developers and system administrators alike, ensuring your services are accessible through a single entry point is often the preferred way to go. This concept is where Ingress resources come into play. Today, we’ll explore how to set up Ingress in your Kubernetes cluster using either Traefik or NGINX to route traffic efficiently to your various services.

Understanding the Need for Ingress

When utilizing Kubernetes, especially with a lightweight installation like K3s, setting up a proper Ingress configuration allows you to:

Simplify external access to your applications without exposing multiple IP addresses.

Route requests based on prefixes, enabling you to host multiple services under a single IP address seamlessly.

In our example, imagine you want to access services like Apache proxies, Java Spring applications, WordPress sites, and more through specific prefixes. Instead of accessing each service via its IP, routing them through a common URL structure (e.g., http://{my-ip}/service1) makes management simpler and cleaner.

Getting Started with Traefik Ingress

To set up Ingress with Traefik in K3s, you will first need to ensure you are working on a compatible version—which, in this case, is K3s v1.25.6 using Traefik v2. The strength of Traefik lies in its middleware features, particularly the ability to manipulate request paths.

Step-by-Step Configuration

Create Middleware for Strip Prefix

This step involves setting up a middleware that will strip the specified prefix from incoming requests, allowing requests made to /service1 to be routed appropriately to the root of the service.

Here’s how the ingress.yaml file looks:

[[See Video to Reveal this Text or Code Snippet]]

Annotations Explained

kubernetes.io/ingress.class: Specifies the class of the Ingress being used, which in this case is Traefik.

traefik.ingress.kubernetes.io/router.middlewares: Assigns the middleware defined to the Ingress resource. Here, you specify the namespace of the middleware you created (in our case, it’s in the default namespace).

Final Considerations

It's important to verify that the path is stripped correctly during routing. While configuring your Ingress, ensure that:

The services are properly named and correspond to the Ports specified (numbering is crucial).

You might need to explore headers further to discover if the original path is preserved, which could be useful for logging or diagnostics.

Conclusion

With the emergence of microservices and container orchestration, Ingress controllers like Traefik and NGINX have become absolutely vital for streamlining access to your applications. With this guide, you should be able to set up a clean Ingress routing system that simplifies access to multiple applications running on your Kubernetes cluster. Whether handling a small set of services or scaling to accommodate more complex use cases, a well-configured Ingress setup can make managing your environment a breeze.

For those navigating Kubernetes for the first time, this might seem a bit daunting, but with practice and careful implementation, it becomes second nature. Thank you for joining me in this exploration of Kubernetes Ingress!