Enabling default Compute Cluster for new environments
When creating your environment, you can enable the default Compute Cluster using the Management Console or CDP CLI to be able to run your data and shared services on the containerized platform.
Required role: EnvironmentAdmin
Before you begin
- Ensure that your Azure account has all the resources required by CDP.
For more information, see Azure subscription requirements.
Using Management Console
When creating your environment in Management Console, ensure
that you use the Enable Compute Cluster setting to create the
Compute Cluster enabled environment.
After completing the step for Data Access and Data Lake Scaling,
configure the networking settings for Kubernetes with enabling User
Defined Routing, and selecting Private Kubernetes
Cluster or providing Authorized IP Ranges on the
Region, Networking and Security page. When selecting
Private Kubernetes Cluster, you also need to select an
existing private DNS zone or select creating a new private DNS zone by CDP on your
Azure account for the database. Worker Node Subnets are
automatically pre-filled with the same set of subnets provided in
Network section, but you have the option to not use all of
the available subnets.For more information about creating your environment, see the Registering environment (UI)
documentation.
Using CDP CLI
Run the following command to create the Compute Cluster enabled environment:
cdp environments create-azure-environment \
--environment-name [***ENVIRONMENT NAME***] \
--credential-name [***CREDENTIAL NAME***] \
--region [***REGION***] \
--public-key [***PUBLIC SSH KEY***] \
--security-access [***SECURITY ACCESS CONFIGURATION***] \
--use-public-ip | --no-use-public-ip \
--log-storage [***STORAGE CONFIGURATION***] \
--enable-compute-cluster \
--compute-cluster-configuration \
privateCluster=false, \
kubeApiAuthorizedIpRanges=[***CIDR1***],[***CIDR2***]
workerNodeSubnets=[***SUBNET1***],[***SUBNET2***]
cdp environments create-azure-environment \
--environment-name [***ENVIRONMENT NAME***] \
--credential-name [***CREDENTIAL NAME***] \
--region [***REGION***] \
--public-key [***PUBLIC SSH KEY***] \
--security-access [***SECURITY ACCESS CONFIGURATION***] \
--use-public-ip | --no-use-public-ip \
--log-storage [***STORAGE CONFIGURATION***] \
--enable-compute-cluster \
--compute-cluster-configuration \
privateCluster=true
workerNodeSubnets=[***SUBNET1***],[***SUBNET2***]
After the command runs, you can verify if the environment was successfully created
with the default Compute Cluster with using the following commands:
- Describing the
environment:
cdp environments describe-environment --env-name-or-crn [***ENVIRONMENT NAME OR CRN***] ... "azureComputeClusterConfiguration": { "privateCluster": false, "kubeApiAuthorizedIpRanges": [ "0.0.0.0/0" ] }, "enableComputeCluster": "true" ...
- Listing Compute
Clusters:
cdp compute list-clusters --env-name-or-crn [***ENVIRONMENT NAME OR CRN***]
You can use the following command to retry the environment creation with the default Compute Cluster:
cdp environments initialize-azure-compute-cluster
--environment-name [***ENVIRONMENT NAME***] \
--compute-cluster-configuration \
privateCluster=false, \
kubeApiAuthorizedIpRanges=[***CIDR1***],[***CIDR2***]
workerNodeSubnets=[***SUBNET1***],[***SUBNET2***]
cdp environments initialize-azure-compute-cluster
--environment-name [***ENVIRONMENT NAME***] \
--compute-cluster-configuration \
privateCluster=true
workerNodeSubnets=[***SUBNET1***],[***SUBNET2***]