-
Notifications
You must be signed in to change notification settings - Fork 80
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
[Bug] : RBAC Permissions #252
Comments
I believe this occurs on an upgrade scenario as we have modified the rbac completely Alternatively run this step
Let me know how you get on |
I add below rbac rule to the clusterrole "xxx-manager-role", problem solved
|
Thank you. I will continue to help K8sGpt become a better open source through many tests. |
@AlexsJones I was thinking that it makes sense to remove cluster role and cluster role binding from our code base and move it as part of the helm chart, wdyt ? |
@junskeep can you share your K8sGPT manifest please? |
The actual issue is coming from K8s behavior with updating/creating roles. The RBAC API prevents users from escalating privileges by editing roles or role bindings. Because this is enforced at the API level, it applies even when the RBAC authorizer is not in use. |
There were no modifications other than this code.
|
I raised a PR to fix the RBAC and in the meantime we can work on this feature to manage RBAC controls from Helm |
There is a fix now, please upgrade to latest operator's version. |
Checklist
Affected Components
K8sGPT Version
v0.0.22
Kubernetes Version
v1.26.8 (EKS)
Host OS and its Version
No response
Steps to reproduce
Previously, I installed and used the CLI with the operator, but I modified the configuration file by activating Slack. There was no notification in the slack, and this error occurred in the operator pod.
Expected behaviour
Successful Slack Notification
Actual behaviour
Additional Information
I followed the existing guide, and I also proceeded with the reinstallation, but I couldn't solve it.
The text was updated successfully, but these errors were encountered: