Kubernetes zones enable cloud administrators to define policy-based placement of Kubernetes clusters and namespaces used in vRealize Automation Cloud Assembly deployments. An administrator can use this page to specify what clusters are available for provisioning of Kubernetes namespaces and what properties are acceptable for clusters.
Cloud administrators can associate Kubernetes zones with PKS cloud accounts configured for Cloud Assembly or with external Kubernetes clusters that are not associated with a project.
When you create a Kubernetes zone, you can assign multiple provider-specific resources to the zone, and these resources will dictate what properties can be set for the newly provisioned clusters in terms of the number of workers, masters, available CPU, memory, and other configuration settings. For PKS providers, these correspond to PKS plans. An administrator can also assign multiple clusters to a Kubernetes zone that will be used for placement of newly provisioned Kubernetes namespaces. The administrator can only assign clusters that are not onboarded, or not managed by CMX, and are provisioned via the preselected cluster provider. The administrator can assign multiple Kubernetes zones to a single project, thus making them all available for placement operations that happen within this project.
A cloud administrator can assign priorities on multiple levels.
- Kubernetes zone priority within a project.
- Resource priority within a Kubernetes zone.
- Cluster priority within a Kubernetes zone.
The cloud administrator can also assign tags on multiple levels:
- Capability tags per Kubernetes zone.
- Tags per resource assignment.
- Tags per cluster assignment.
Service Broker contains a version of the Kubernetes Zone page to enable Service Broker administrators to access existing Kubernetes zones so they can create placement policies for Kubernetes namespaces and clusters provisioned from the catalog.
Configure integration with a suitable PKS deployment. See Configure PKS Integration in vRealize Automation Cloud Assembly
- Select New Kubernetes Zone. and click
- Enter the PKS integration Account name to which you want this zone to apply.
- Add a Name and Description for the Kubernetes Zone.
- Add capability tags if appropriate. See Using capability tags in vRealize Automation Cloud Assembly for more information.
- Click Save.
- Click the On-demand tab and add PKS plans as appropriate for the zone to use for cluster provisioning.
You can select one or more plans and assign priorities to them. Lower numbers equal higher priority. Priority assignments are secondary to tag based selection.
- Click the Cluster tab and then click the Add button to add Kubernetes clusters to the zone. If you are working with an external cluster, it is automatically onboarded to vRealize Automation Cloud Assembly when you select it.
You can add Kubernetes namespaces to the cluster on the Kubernetes Clusters page in vRealize Automation Cloud Assembly.
Kubernetes zones are configured for use with vRealize Automation Cloud Assembly deployments.
What to do next
Assign the Kubernetes zone to a project.
- Select and then select the project that you want to associate with your Kubernetes zone.
- Click the Kubernetes Provisioning tab on the Project page.
- Click Add Kubernetes Zone and add the zone that you just created. You can multiple zones if appliacable, and you also set the priority on the zones.
- Click Save.
After you assign a zone to a project, you can use the Blueprints page to provision a deployment based on the Kubernetes zone and project configuration.