-
-
Notifications
You must be signed in to change notification settings - Fork 460
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] Add access to traefik dashboard #103
Comments
Hi there, thanks for opening this feature request. I don't think, that this is an issue for k3d though, but rather for k3s. [api]
dashboard = true -> then save this and exit. Then delete the existing traefik pod or wait until it reloads the config. Then to access it from your machine, you can do one of the following: a) use Hope this helps so far 👍 |
@iwilltry42 it helped for sure, I had access. Thanks. As it's more related to k3s, should I create an issue on their repo? I'm sure others would like to access this UI more easily. |
I'm not a maintainer of k3s, but if you think, it'd add enough value, then go ahead and open an issue over there 👍 |
I'll go ahead and close this issue over here 👍 |
Btw, just adding |
I know this issue is closed but I found another way to do this which hopefully helps others. I created my k3d cluster with the following command, contextually this is important as I bind my cluster to port 8081 on my local interface. k3d cluster create -p "8081:80@loadbalancer" So I followed the step above and jump on the running master node and edit the docker exec -it <container_name> /bin/sh By default the helm chart creates the first ingress (below) with host traefik.example.com by default if you don't provide the domain configuration option. If you do provide the domain it substitutes it for the default domain. NAME CLASS HOSTS ADDRESS PORTS AGE
traefik-dashboard <none> traefik.example.com 192.168.48.2 80 38m
traefik-dashboard-path <none> * 192.168.48.2 80 4m22s I don't want to always port forward so I simply ignore the ingress created by the helm chart and create my own custom path based ingress. Basically using the proxy 8081 -> 80 setup by k3d when I created the cluster to get my request to the traefik ingress controller. ---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: traefik-dashboard-path
annotations:
ingress.kubernetes.io/ssl-redirect: "false"
traefik.ingress.kubernetes.io/rule-type: "PathPrefixStrip"
spec:
rules:
- http:
paths:
- path: /traefik
pathType: Exact
backend:
service:
name: traefik-dashboard
port:
number: 80 You should now be able to access the dashboard on localhost at the following address: |
Is your feature request related to a problem or a Pull Request?
N/A
Scope of your request
I saw that traefik is used as ingress controller, which's great. Should be great to get an access to its dashboard.
Describe the solution you'd like
Expose port 8080 for access to traefik's webui (dashboard)
Describe alternatives you've considered
N/A
The text was updated successfully, but these errors were encountered: