Kubernetes 1.23 - Traefik `ServiceAccount` is unable to list CRDs
See original GitHub issueWhat happened:
Hi everyone! I’ve deployed daskhub helm chart to k8s 1.23. I ran into the same error message from https://github.com/dask/dask-gateway/issues/469, so I updated the Traefik CRD and updated the Traefik version to 2.6 by following the changes in this recent commit . I no longer get the Traefik pod error from https://github.com/dask/dask-gateway/issues/469, but now its logging rbac/permission errors related to the Traefik ServiceAccount
being unable to list the Traefik CRDs:
Failed to watch *v1alpha1.IngressRouteUDP: failed to list *v1alpha1.IngressRouteUDP: ingressrouteudps.traefik.containo.us is forbidden: User "system:serviceaccount:daskhub:traefik-daskhub-dask-gateway" cannot list resource "ingressrouteudps" in API group "traefik.containo.us" at the cluster scope
Failed to watch *v1alpha1.ServersTransport: failed to list *v1alpha1.ServersTransport: serverstransports.traefik.containo.us is forbidden: User "system:serviceaccount:daskhub:traefik-daskhub-dask-gateway" cannot list resource "serverstransports" in API group "traefik.containo.us" at the cluster scope
This continues for the other Traefik CRDs.
What you expected to happen:
I expected there to be issues trying this out with the latest k8s release. I just wanted to open an issue to track this, and help out with a fix in any way I can!
Anything else we need to know?:
Related to https://github.com/dask/dask-gateway/issues/469
Environment:
- Kubernetes: 1.23
- Daskhub helm chart
- dask/distributed version: 2022.1.0
Helm Chart values.yaml
:
# The image to use for the proxy pod
image:
name: traefik
tag: 2.6
- traefik CRD from https://github.com/dask/dask-gateway/commit/fd77685a592b91fa90c8fe77fee42b154a1144f3
- Python version: 3.9
- Operating System: Ubuntu 20.04.3 LTS
- Install method (conda, pip, source): conda
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (5 by maintainers)
Top GitHub Comments
@consideRatio that worked! Thank you!
Ah, of course. Indeed, my testing was against the chart rendered directly from the repo. Thanks for looking into it. So we need a release!!!