Understanding the Personas of Alana, Cody and Naomi within Pivotal Container Service (PKS)
Article ID: 298585
Updated On:
Products
VMware Tanzu Kubernetes Grid Integrated Edition
Issue/Introduction
When someone refers to the Personas (names) of Alana, Cody or Naomi within PKS, this article will help explain what they are referring to.
Environment
Product Version: 1.2
Resolution
At the end of this section is a helpful diagram of three Personas who interact and work with Pivotal Container Service (PKS).
Three Personas are:
Alana:
Alana is a PKS Administrator and Operator. This person is involved in the following aspects of Pivotal Container Service:
- Initial PKS Deployment and Installation activities
- PKS platform upgrades and systems patches
- PKS Tile Administration and the PKS control plane
- Setting PKS Role-Based Access Control for the PKS control plane.
- Alana is the persona who provides access and authorization to any of the PKS Cluster Administrators.
Cody:
Cody has the ability to create a PKS cluster and become its PKS cluster Admin. This person is involved in the following aspects of Pivotal Container Service:
- Can create a PKS cluster through mechanism of pks cli: pks create-cluster ...
- Can be the PKS Cluster Administrator.
- Sets Kubernetes Role-Based Access Control to a specific PKS Cluster for End-users and Developers within the Kubernetes control plane.
- Example: If an end-user or developer (Naomi persona) requests a new namespace or to become the equivalent of namespace admin, the Cody (admin) persona would perform these actions on behalf of Naomi. Cody performs the actions such as adding the role/clusterrole, rolebindings/clusterrolbindings for Naomi to be able to access the cluster and/or administer the namespace.
Naomi:
Naomi is an end-user or developer on a Kubernetes cluster. This person is involved in the following aspects of Pivotal Container Service:
- Access a Kubernetes API for the cluster they have access to
- Can use the kubectl cli, Kubernetes Dashboard, or other Kubernetes API to interact with a specific PKS Cluster
Three Personas are:
Alana:
Alana is a PKS Administrator and Operator. This person is involved in the following aspects of Pivotal Container Service:
- Initial PKS Deployment and Installation activities
- PKS platform upgrades and systems patches
- PKS Tile Administration and the PKS control plane
- Setting PKS Role-Based Access Control for the PKS control plane.
- Alana is the persona who provides access and authorization to any of the PKS Cluster Administrators.
Cody:
Cody has the ability to create a PKS cluster and become its PKS cluster Admin. This person is involved in the following aspects of Pivotal Container Service:
- Can create a PKS cluster through mechanism of pks cli: pks create-cluster ...
- Can be the PKS Cluster Administrator.
- Sets Kubernetes Role-Based Access Control to a specific PKS Cluster for End-users and Developers within the Kubernetes control plane.
- Example: If an end-user or developer (Naomi persona) requests a new namespace or to become the equivalent of namespace admin, the Cody (admin) persona would perform these actions on behalf of Naomi. Cody performs the actions such as adding the role/clusterrole, rolebindings/clusterrolbindings for Naomi to be able to access the cluster and/or administer the namespace.
Naomi:
Naomi is an end-user or developer on a Kubernetes cluster. This person is involved in the following aspects of Pivotal Container Service:
- Access a Kubernetes API for the cluster they have access to
- Can use the kubectl cli, Kubernetes Dashboard, or other Kubernetes API to interact with a specific PKS Cluster
Feedback
Yes
No
Powered by
