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.
Ensure that you have Beta CDP CLI installed. For more information, see the Installing Beta CDP CLI documentation.

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.

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:

Without private cluster
With private cluster

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***]

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

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:

Without private cluster
With private cluster

cdp environments initialize-azure-compute-cluster 
--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***]

cdp environments initialize-azure-compute-cluster 
--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