Skip to content

GitLab Next

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 2
    • Merge requests 2
  • Requirements
    • Requirements
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #55902

You need to sign in or sign up before continuing.
Closed
Open
Created Jan 03, 2019 by Daniel Gruesso@danielgruessoContributor

Remove support for creating non-RBAC kubernetes clusters

Problem to solve

Currently, users are offered the option to create a non-RBAC k8s cluster. This is counter to current k8s best practices and gives room for error when used in conjunction with other services (ie knative)

Target audience

Operators, developers

Further details

Proposal

On cluster creation, remove the RBAC-enabled cluster option, so that all clusters are created with RBAC enabled by default. If user wishes to remove rbac they can still do so from the command line.

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

Links / references

Edited Feb 25, 2019 by Daniel Gruesso
Assignee
Assign to
Time tracking