Getting Started with General Kubernetes Functionality
The Kubernetes workflow allows you to add dedicated hosts, create one or more clusters, add one or more tenants to a cluster, and then create virtual nodes/containers that run in virtual clusters (pods) to run Kubernetes applications. This workflow consists of three high-level steps that must be performed by users with different roles in the following order:
- Kubernetes Administrator
- Kubernetes Cluster Administrator
- Kubernetes Tenant/Project Administrator
- Kubernetes Tenant Member
Kubernetes Administrator
- Log into the web interface as a Kubernetes Administrator, as described in Launching and Logging In.
- Verify that HPE Ezmeral Runtime Enterprise is licensed for at least the number of CPU cores that will be used for the new Kubernetes cluster. See and License Tab.
- If needed, configure LDAP/AD authentication.
- If you will be using HPE Ezmeral Data Fabric on Kubernetes and have not done so already, then add one or more data fabric nodes, as described in Kubernetes Data Fabric Node Installation Overview. See also About HPE Ezmeral Data Fabric on Kubernetes.
- Add one or more Kubernetes Worker hosts, as described in Kubernetes Worker Installation Overview.
- If one does not already exist and if you will be using HPE Ezmeral Data Fabric on Kubernetes, then create a Data Fabric cluster, as described in Creating a New Data Fabric Cluster. You may create a single Data Fabric cluster per HPE Ezmeral Runtime Enterprise deployment. If needed, you may expand an existing Data Fabric cluster, as described in Expanding a Data Fabric Cluster.
- Create a Kubernetes cluster, as described in Creating a New Kubernetes Cluster.
- Assign at least one user to be a Kubernetes Administrator for the Kubernetes cluster you just created. See Managing Kubernetes Admin Users (to assign a user role using local authentication) or Updating External Kubernetes Administrator Groups (to assign a user role using LDAP/AD groups).
Kubernetes Cluster Administrator
- Confirm that the Kubernetes Administrator has completed all of the steps described in Kubernetes Administrator, above.
- Log in to the web interface as a Kubernetes Cluster Administrator, as described in Launching and Logging In.
- If needed, use the Kubernetes Dashboard and/or Web Terminal to configure the Kubernetes cluster, as described in Accessing the Kubernetes Dashboard and Kubernetes Web Terminal, respectively. See Kubernetes Tenant RBAC for the privileges allowed to Kubernetes Cluster Administrator users.
- Assign the Kubernetes Tenant Administrator and/or Kubernetes Member roles to the appropriate users, as described in Viewing and Assigning Kubernetes Cluster Users.
Kubernetes Tenant Administrator
- Confirm that the Kubernetes Cluster Administrator has completed all of the steps described in Kubernetes Cluster Administrator, above.
- If needed, use the Kubernetes Dashboard and/or Web Terminal to configure the Kubernetes cluster, as described in Accessing the Kubernetes Dashboard and Kubernetes Web Terminal, respectively. See Kubernetes Tenant RBAC for the privileges allowed to Kubernetes Tenant Administrator users.
- Create one or more DataTaps to allow the tenant to access remote data storage resources. See About DataTaps and Creating a New DataTap.
- Assign one or more Kubernetes Member roles to the appropriate users, as described in Viewing and Assigning Kubernetes Tenant Users.
Kubernetes Tenant Member
- Confirm that the Kubernetes Tenant Administrator has completed all of the steps described in Kubernetes Tenant Administrator, above.
- Log in to the web interface as the Kubernetes Member user that was created or assigned in Step 4 of the Kubernetes Tenant Administrator workflow described above.
- Either:
- Deploy KubeDirector apps, as described in Deploying KubeDirector Apps.
- Onboard Kubectl apps, as described in Onboarding Kubectl Apps.
You may also use the Kubernetes Dashboard and/or Web Terminal to deploy Kubernetes objects such as pods, as described in Accessing the Kubernetes Dashboard and Kubernetes Web Terminal, respectively. See Kubernetes Tenant RBAC for the privileges allowed to Kubernetes Tenant Member users.