Why is the prevention of self provisioning of OpenShift projects rolled back automatically?

Solution Verified - Updated -

Issue

  • Even if we prohibited self provisioning of projects, the settings have been automatically rolled back and the users on OpenShift can create their projects by themselves.
  • When removing the self-provisioner role from cluster groups, this warning message appears:

    Warning: Your changes may get lost whenever a master is restarted, unless you prevent reconciliation of this rolebinding using the following command: oc annotate clusterrolebinding.rbac self-provisioners 'rbac.authorization.kubernetes.io/autoupdate=false' --overwritecluster role "self-provisioner" removed: ["system:authenticated" "system:authenticated:oauth"]
    

Environment

  • Red Hat OpenShift Container Platform (OCP) 3.11

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content