-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
doc: example 'external-dns' v1.1.8 does not work on IRSA #1289
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Since v1.1.8 the example of 'external-doc' uses
bitnami/external-dns
that uses user1001
to run the external-dns process who does not has permission to read web identity token. It's also a known issue of aws/amazon-eks-pod-identity-webhook#8 pending on upstream kubernetes.There is a workaround
kubernetes-sigs/external-dns#1185 (comment) to grant the permission.
The text was updated successfully, but these errors were encountered: