Traefik

Getting started with Traefik on cegedim.cloud — deploying workloads with IngressRoute

Traefik v3 supports the Kubernetes Gateway API natively. It also provides its own IngressRoute CRD for teams who prefer Traefik-native routing. This guide uses IngressRoute as a practical entry point.

Kubernetes IngressRoute - Traefikdoc.traefik.io

What the platform provides

You do not need to install or configure Traefik. The following are deployed and managed by the platform team:

Component

Role

Traefik controller

Watches IngressRoute/HTTPRoute resources cluster-wide

web entry point

HTTP entry point — receives traffic forwarded by the F5 BigIP

Each cegedim.cloud cluster is fronted by an F5 BigIP load balancer that handles wildcard DNS (*.{{ cluster-name }}.ccs.cegedim.cloud), TLS termination, and L4 forwarding to the Traefik pods. Replace {{ cluster-name }} with your actual cluster name (e.g. prod-paris, staging-lyon) in all examples below.

Deploying your application

Prerequisites

Traefik is installed on your cluster (available from the platform team via ITCare)

Step 1 — Deploy your workload

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-web
spec:
  replicas: 2
  selector:
    matchLabels:
      app: nginx-web
  template:
    metadata:
      labels:
        app: nginx-web
    spec:
      containers:
      - name: nginx
        image: nginx:stable
        ports:
        - containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: nginx-web
spec:
  selector:
    app: nginx-web
  ports:
  - port: 80
    targetPort: 80

Step 2 — Create the IngressRoute

apiVersion: traefik.io/v1alpha1
kind: IngressRoute
metadata:
  name: nginx-web
spec:
  entryPoints:
    - web
  routes:
    - match: Host(`nginx-web.{{ cluster-name }}.ccs.cegedim.cloud`)
      kind: Rule
      services:
        - name: nginx-web
          port: 80

Step 3 — Verify

# Check the IngressRoute status
kubectl get ingressroute nginx-web

# Test the endpoint
curl https://nginx-web.{{ cluster-name }}.ccs.cegedim.cloud/

Alternative: Gateway API HTTPRoute

If you prefer to use the standard Kubernetes Gateway API instead of the Traefik-native IngressRoute, Traefik v3 supports HTTPRoute natively. The platform provides a traefik-int Gateway for internal traffic.

apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: nginx-web
spec:
  parentRefs:
  - name: traefik-int
  hostnames:
  - "nginx-web.{{ cluster-name }}.ccs.cegedim.cloud"
  rules:
  - matches:
    - path:
        type: PathPrefix
        value: /
    backendRefs:
    - name: nginx-web
      port: 80

# Check the HTTPRoute status
kubectl get httproute nginx-web

# Test the endpoint
curl https://nginx-web.{{ cluster-name }}.ccs.cegedim.cloud/

Clean up

If you used IngressRoute:

kubectl delete ingressroute nginx-web
kubectl delete service nginx-web
kubectl delete deployment nginx-web

If you used HTTPRoute:

kubectl delete httproute nginx-web
kubectl delete service nginx-web
kubectl delete deployment nginx-web