I have a few questions about Traefik on Kubernetes:
- Can I expose the dashboard only via kubectl port-forward or some other tunneled method so it is not accessible to the wide internet? The example in the docs uses basic auth and is exposed to the internet it seems…
- Since Gateway API currently has the certificates on the Gateway object, and ListenerSets are really new (Not sure if even released…) so not really implemented in Traefik, or other gateways just yet, what’s the best way to handle certificates when deploying multiple apps? Do you create multiple Gateways or edit the one Gateway? If I create multiple Gateways, how does Traefik handle that? (The mapping between gateway resources and the actual load balancers seems rather evolving currently in the spec.
- Should I let each app create its own gateway? what’s the current convention here when creating resource templates/charts for apps? (The current examples in the docs site have the Traefik Helm chart create a gateway).
- I think if you don’t define sectionName in your HTTPRoute it will add the route to all listeners, but since
webin the example is set to automatically redirect to HTTPS having any other routes on it seems redundant, so why are some examples without specifyingsectionName?