Where did traefik configmap go?

[ericis]

*Cross-posted to StackOverflow, to a thread in Rancher forums, and to traefik's community discussion board

Tutorials from 2020 refer to editing the traefik configmap. Where did it go?

No configmap in use by traefik deployment

For a 2-server, 2-agent cluster... kubectl -n kube-system describe deploy traefik does not show any configmap:

  Volumes:
   data:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:     
    SizeLimit:  <unset>
   tmp:
    Type:               EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:             
    SizeLimit:          <unset>
  Priority Class Name:  system-cluster-critical

No "traefik" configmap

And, kubectl get -n kube-system cm shows:

NAME                                 DATA   AGE
chart-content-traefik                0      28m
chart-content-traefik-crd            0      28m
chart-values-traefik                 1      28m
chart-values-traefik-crd             0      28m
cluster-dns                          2      28m
coredns                              2      28m
extension-apiserver-authentication   6      28m
k3s                                  0      28m
k3s-etcd-snapshots                   0      28m
kube-root-ca.crt                     1      27m
local-path-config                    4      28m

No configmap in use by traefik pods

Describing the pod doesn't turn up anything either. kubectl -n kube-system describe pod traefik-.... results in no configmap too.

Traefik ports in use, but not responding

However, I did see arguments to the traefik pod with ports in use:

      --entryPoints.traefik.address=:9000/tcp
      --entryPoints.web.address=:8000/tcp
      --entryPoints.websecure.address=:8443/tcp

However, these ports are not exposed. So, I tried port-forward with kubectl port-forward pods/traefik-97b44b794-r9srz 9000:9000 8000:8000 8443:8443 -n kube-system --address 0.0.0.0, but when I curl -v localhost:9000 (or 8000 or 8443) and curl -v localhost:9000/dashboard, I get "404 Not Found".

After getting a terminal to traefik, I discovered the local ports that are open, but it seems nothing is responding:

/ $ netstat -lntu
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       
tcp        0      0 :::8443                 :::*                    LISTEN      
tcp        0      0 :::8000                 :::*                    LISTEN      
tcp        0      0 :::9000                 :::*                    LISTEN      
/ $ wget localhost:9000
Connecting to localhost:9000 ([::1]:9000)
wget: server returned error: HTTP/1.1 404 Not Found
/ $ wget localhost:8000
Connecting to localhost:8000 ([::1]:8000)
wget: server returned error: HTTP/1.1 404 Not Found
/ $ wget localhost:8443
Connecting to localhost:8443 ([::1]:8443)
wget: server returned error: HTTP/1.1 404 Not Found

Versions

k3d version v4.4.7
k3s version v1.21.2-k3s1 (default)

[iwilltry42]

Hi @ericis , thanks for starting this discussion!
So what do you want to do?

Traefik is the ingress controller configured by Kubernetes Ingress resources, so it doesn't use a static configuration (ConfigMap). All required config options are set via flags in the deployment (e.g. listening ports).

Those ports are exposed using a Kubernetes Service of type LoadBalancer, which is realized by the Klipper servicelb in the cluster binding to the respective hostPorts on the k3s containers (k3d nodes).

UPDATE: to expose the dashboards (port 9000), you could e.g. start the cluster with --port 9000:9000 and modify the traefik service to include that port as well.