Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,332
    • Merge requests 1,332
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #31113
You need to sign in or sign up before continuing.
Closed
Open
Issue created Aug 21, 2019 by Bastian Blank@waldiContributor

Create Kubernetes service account with role admin

Problem to solve

The service account created by the Kubernetes integration should be able to create further service accounts, roles and role bindings to deploy applications that need to communicate with Kubernetes.

Intended users

Unknown

Further details

Currently service accounts are created with the cluster role edit, which is automatically maintained and contains access all normal objects. It does however not include access to roles and role bindings.

This means that deploying and testing permission changes, even within this one namespace, can't be done via the Kubernetes integration. This can be fixed by applying the admin cluster role, which includes access to those objects.

Proposal

Change Clusters::Gcp::Kubernetes::PROJECT_CLUSTER_ROLE_NAME to admin.

Permissions and Security

Documentation

Update "Environment namespace" row in https://docs.gitlab.com/ee/user/project/clusters/add_remove_clusters.html#rbac-cluster-resources

Testing

What does success look like, and how can we measure that?

Links / references

Edited Oct 19, 2020 by Thong Kuah
Assignee
Assign to
Time tracking