-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
[bitnami/external-dns] Add traefik-proxy rules to external-dns helm chart #19211
Comments
Thank you for opening this issue and submitting the associated Pull Request. Our team will review and provide feedback. Once the PR is merged, the issue will automatically close. Your contribution is greatly appreciated! |
This will be fixed by #19168. I closed my PR because is a duplicate of an earlier one. |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Name and Version
bitnami/external-dns 6.24.3
What is the problem this feature will solve?
To work with traefik, the ClusterRole needs access to its CRDs.
What is the feature you are proposing to solve the problem?
Add the RBAC as external-dns did in their own helm chart, implemented in this PR: kubernetes-sigs/external-dns#3325
What alternatives have you considered?
Moving to external-dns own helm charts, but I found rfc2136 bitnami implementation better, and want to stick with it.
The text was updated successfully, but these errors were encountered: