Illumina Innovates with Rancher and Kubernetes
These example scenarios describe how an organization could use templates to standardize cluster creation.
Let’s say there is an organization in which the administrators decide that all new clusters should be created with Kubernetes version 1.14.
In this way, the administrators enforce the Kubernetes version across the organization, while still allowing end users to configure everything else.
Let’s say an organization has both basic and advanced users. Administrators want the basic users to be required to use a template, while the advanced users and administrators create their clusters however they want.
The administrator then creates two templates:
The administrator shares the advanced template with only the advanced users.
The administrator makes the template for basic users public, so the more restrictive template is an option for everyone who creates a Rancher-provisioned cluster.
Result: All Rancher users, except for administrators, are required to use a template when creating a cluster. Everyone has access to the restrictive template, but only advanced users have permission to use the more permissive template. The basic users are more restricted, while advanced users have more freedom when configuring their Kubernetes clusters.
Let’s say an organization has a template that requires clusters to use Kubernetes v1.14. However, as time goes on, the administrators change their minds. They decide they want users to be able to upgrade their clusters to use newer versions of Kubernetes.
In this organization, many clusters were created with a template that requires Kubernetes v1.14. Because the template does not allow that setting to be overridden, the users who created the cluster cannot directly edit that setting.
The template owner has several options for allowing the cluster creators to upgrade Kubernetes on their clusters:
Let’s say Alice is a Rancher administrator. She owns an RKE template that reflects her organization’s agreed-upon best practices for creating a cluster.
Bob is an advanced user who can make informed decisions about cluster configuration. Alice trusts Bob to create new revisions of her template as the best practices get updated over time. Therefore, she decides to make Bob an owner of the template.
To share ownership of the template with Bob, Alice adds Bob as an owner of her template.
The result is that as a template owner, Bob is in charge of version control for that template. Bob can now do all of the following: