-
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
It seems the cluster it is running with Authorization enabled (like RBAC) and there is no permissions for the ingress controller. Please check the configuration #305
Comments
I am experienced same issue as well. |
I saw some issues with the controller in my 1.8 rbac-enabled cluster. I submitted a PR (#291) a few months back with the change i needed to make, you could try apply thing to your instance @rremella + @hmarcelodn |
@tyrannasaurusbanks @rremella or @hmarcelodn did that work for you? I'm experiencing the same issues. |
This should solve your issue https://github.com/raf-d/aws-alb-controller/blob/master/RBAC-for-aws-controller.md |
@raf-d do you mind sending in a PR with that RBAC info? it would help out to have it in the docs. |
We've got RBAC docs in the examples folder now: https://github.com/kubernetes-sigs/aws-alb-ingress-controller/blob/master/examples/rbac-role.yaml |
I am using kubernetes 1.9 version getting below issue , the alb-ingress controller is going on crashloop
It seems the cluster it is running with Authorization enabled (like RBAC) and there is no permissions for the ingress controller. Please check the configuration
Can anyone let me how to resolve this issue ? Is there any permissions I need to set ?
The text was updated successfully, but these errors were encountered: