Configure Kubernetes permission of the application (Kube RBAC)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- kubernetes
- Domain
- authorization, infrastructure
Research direction
Start with the Kubernetes RBAC documentation linked in the issue and identify how the application’s desired permissions should map to Roles, ClusterRoles, RoleBindings, and ClusterRoleBindings. Define the configuration surface and the generated resources; done means an application can receive the requested permissions on its cluster without exceeding them.
Written by the indexing model from the issue text.
Description
As of today, any pod deployed by Qovery on your kubernetes cluster has the minimum set of permissions that can be given to a pod.
With this feature, we will let you configure the RBAC kubernetes authorization (https://kubernetes.io/docs/reference/access-authn-authz/rbac/ [https://kubernetes.io/docs/reference/access-authn-authz/rbac/]) assigned to the application, providing it special permissions on the cluster (list pods, create new pods etc..). We will automatically create the Role, ClusterRole, RoleBinding and ClusterRoleBinding on your cluster based on the desired permissions.
Votes: 2 | Submitted: 2023-07-04 | Featurebase: https://roadmap.qovery.com/p/configure-kubernetes-permission-of-the-application-kube-rbac-4 | Author: Alessandro Carrano | Jira: https://qovery.atlassian.net/browse/QOV-784
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Qovery/Roadmap
-
testtt Open
Difficulty 5/5 Over a week Newbie friendliness 10/100
-
test Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
status: reviewing
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
status: canceled
Difficulty 5/5 Over a week Newbie friendliness 30/100
Similar issues
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getgrav/grav-plugin-api#45 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sisaku-security/sisakulint#647 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yunaremaia/driftcheck#246 ·
-
bug good-first-issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
yunaremaia/taintrace#110 ·