Traefik Kubernetes: How to Expose Non-Kubernetes Services

Traefik Kubernetes: How to Expose Non-Kubernetes Services

In the world of container orchestration, Kubernetes has emerged as a leading platform. However, managing services that are not part of the Kubernetes ecosystem can be a challenge. This is where Traefik, a modern HTTP reverse proxy and load balancer, comes into play. In this blog post, we’ll explore how to expose non-Kubernetes services using Traefik in a Kubernetes environment.

What is Traefik?

Traefik is an open-source edge router that makes publishing your services a fun and easy experience. It supports several backends (Docker, Swarm, Kubernetes, Marathon, Consul, Etcd, Zookeeper, BoltDB, Rest API, file…) to manage its configuration automatically and dynamically.

Why Traefik for Non-Kubernetes Services?

While Kubernetes provides robust service discovery and routing for applications running within the cluster, it doesn’t natively support non-Kubernetes services. Traefik fills this gap by providing a unified way to route traffic to both Kubernetes and non-Kubernetes services.

Step 1: Install Traefik

First, you need to install Traefik in your Kubernetes cluster. You can do this using Helm, the package manager for Kubernetes.

helm repo add traefik https://helm.traefik.io/traefik
helm repo update
helm install traefik traefik/traefik

Step 2: Configure Traefik for Non-Kubernetes Services

To expose a non-Kubernetes service, you need to define it in Traefik’s static configuration. This can be done in a YAML file, like so:

http:
  routers:
    my-router:
      rule: "Host(`my-service.example.com`)"
      service: "my-service"
  services:
    my-service:
      loadBalancer:
        servers:
        - url: "http://192.168.0.10:80"

In this example, we’re defining a router that routes traffic from my-service.example.com to a service named my-service. The service is defined as a load balancer that sends traffic to http://192.168.0.10:80.

Step 3: Apply the Configuration

To apply this configuration, you need to create a ConfigMap in Kubernetes and mount it in the Traefik pod.

kubectl create configmap traefik-config --from-file=traefik.yaml

Then, update the Traefik deployment to mount the ConfigMap:

...
spec:
  containers:
  - name: traefik
    image: traefik:v2.3
    volumeMounts:
    - name: config
      mountPath: /etc/traefik
      readOnly: true
  volumes:
  - name: config
    configMap:
      name: traefik-config
...

Step 4: Test the Configuration

Finally, you can test the configuration by sending a request to my-service.example.com. If everything is set up correctly, the request should be routed to http://192.168.0.10:80.

curl http://my-service.example.com

Conclusion

Traefik provides a powerful and flexible way to expose non-Kubernetes services in a Kubernetes environment. By defining your services in Traefik’s static configuration, you can route traffic to any IP address or hostname, regardless of whether it’s part of the Kubernetes cluster.

Remember, while this guide provides a basic example, Traefik’s configuration is highly customizable. You can define complex routing rules, integrate with Let’s Encrypt for automatic HTTPS, load balance traffic between multiple servers, and much more.

In the world of Kubernetes, Traefik is a valuable tool for managing and exposing all your services, whether they’re part of the Kubernetes ecosystem or not.

About Saturn Cloud

Saturn Cloud is your all-in-one solution for data science & ML development, deployment, and data pipelines in the cloud. Spin up a notebook with 4TB of RAM, add a GPU, connect to a distributed cluster of workers, and more. Join today and get 150 hours of free compute per month.