Repository navigation
Add Privileged and Non-Privileged RBAC Configurations with Documentation - #812
Conversation
|
Hi @chaitanyaenr, @paigerube14, After some research and navigating through various resources to understand RBAC policies, I’ve successfully created the privileged and non-privileged RBAC configurations for Krkn. My next task is to develop comprehensive documentation for this feature, which I’m currently working on. I have a quick question: Should I also include the Thanks! 😄 |
0c931ca to
4c9cd5b
Compare
|
Thanks so much for this PR! We'll have a review soon, but it looks like there's an issue when you rebased with main. Try using these steps to see if you can rebase https://krkn-chaos.dev/docs/contribution-guidelines/git-pointers/#rebase-with-upstream. We also normally try to have 1 commit per PR if you can squash them into one that would be great! No, the docs should all live in the https://github.com/krkn-chaos/website repo. We're slowly moving them over to there and any new docs we've created are already there. It would be great if you could add the details of these files with links into the docs as well. |
Yepp I read the contribution guidelines mentioning squash all your commits to one, I will rebase my branch with main again and update my PR with only single commit.
Sure will add the documentation for rbac in krkn-chaos/website repo Thankss!! |
Signed-off-by: Abhinav Sharma <abhinavs1920bpl@gmail.com>
f083dd4 to
6293513
Compare
fa80da7 to
6293513
Compare
|
Hi @paigerube14 @shahsahil264 Thanks!! |
Description
This pull request introduces privileged and non-privileged RBAC configurations for Krkn, enabling users to run chaos scenarios based on their access level. It adds YAML files for
Role,ClusterRole,RoleBinding, andClusterRoleBindingin a newrbacdirectory, covering namespace-scoped and cluster-wide permissions.For writing the RBAC policies, I referred to the Kubernetes RBAC documentation (https://kubernetes.io/docs/reference/access-authn-authz/rbac/), Krkn’s scenario documentation (https://krkn-chaos.github.io/krkn/docs/scenarios/), and got refrence from Chaos Mesh’s permission management guide (https://chaos-mesh.org/docs/manage-user-permissions/).
Documentation
If checked, a documentation PR must be created and merged in the website repository.
Related Documentation PR (if applicable)
krkn-chaos/website#66
Issue
It will resolve the issue #759