Derek Coleman & Associates Inc logoDerek Coleman & Associates Inc

Home / Support / Traefik on AKS

Traefik on AKS — Support & Quick Start

Traefik on AKS — Traefik packaged as a Kubernetes application for AKS: a cloud-native ingress controller and reverse proxy (standard Ingress plus IngressRoute/Middleware CRDs) on your own cluster. Published by Derek Coleman & Associates Inc on the Azure Marketplace, deployed in your own Azure sub…

Email support Product page Azure Marketplace listing

At a glance

Application portscluster-internal ClusterIP service by default: 80 (web), 443 (websecure); nothing is internet-facing until you set service.type=LoadBalancer. The API/dashboard is disabled by default
Service(s)Deployment <release> in your namespace; IngressClass <release>; traefik.io CRDs (IngressRoute, Middleware, TLSOption) installed with the chart
Logskubectl logs -n <namespace> deploy/<release>
VersionTraefik 3.7.7 (Helm chart 0.1.0)
PlatformAKS (Kubernetes)

Quick start

  1. Open the offer in the Azure Marketplace and select Get It Now → Create.
  2. Pick your AKS cluster (managed identity enabled) or create a new one, and choose a namespace.
  3. Review + create: the portal installs the Helm-based application onto your cluster.
  4. Verify with `kubectl get pods -n <namespace>`, then expose the service and add your first Ingress (see First login below).

First login

  1. No credential is generated. The Service is ClusterIP: to expose Traefik through an Azure load balancer upgrade the release with `--set service.type=LoadBalancer` (add the azure-load-balancer-internal annotation for a private LB).
  2. Route traffic with a standard Ingress (`spec.ingressClassName: <release>`) or with IngressRoute / Middleware / TLSOption resources.
  3. Health: `kubectl exec -n <namespace> deploy/<release> -- traefik healthcheck --ping`. Keep the dashboard disabled unless it sits behind authentication.

Still stuck?

Email support@dcassociatesgroup.com (response within 1 business day) or send a message via the contact form. Include the offer name, cluster region, and the output of kubectl get pods -n <namespace> and kubectl describe pod <pod> when reporting an issue.