Editing Rancher launched Kubernetes cluster in infrastructure provider restricted to creating user
This document (000020211) is provided subject to the disclaimer at the end of this document.
When attempting to edit a Rancher launched Kubernetes cluster, hosted on nodes in an infrastructure provider neither the
Cluster Options nor
Node Pools sections are available and configurable in the edit cluster view, if logged in as a different user to the cluster creator.
- A Rancher v2.x launched Kubernetes cluster, provisioned on nodes hosted in an infrastructure provider
- Access to the Rancher UI as a user different to the cluster creator
Node templates contain the configuration parameters for provisioning nodes in a specific cloud provider.
Node templates are user-scoped and, as a result, where
userA creates a node template in Rancher it is not accessible by
userB. This prevents Rancher launched Kubernetes clusters, provisioned on nodes in an infrastructure provider by
userA from being edited by other users, as only
userA has access to the node template configuration.
An enhancement request to enable users, other than the cluster creator, to edit Rancher launched Kubernetes clusters is tracked in Rancher GitHub Issue #12038.
Where it is necessary for another user to edit the cluster, i.e. the original user who created the cluster has left the business, it is possible to re-associate the node template with a different user. If you encounter this situation, please open a ticket with Rancher Support for assistance.
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000020211
- Creation Date: 06-May-2021
- Modified Date:06-May-2021
- SUSE Rancher
For questions or concerns with the SUSE Knowledgebase please contact: firstname.lastname@example.org