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 AWS account has all the resources required by CDP.
For more information, see AWS account requirements.
- Ensure that the IAM permissions are correctly set up for your environment.
For more information, see Setting up Compute Cluster IAM permissions.
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 either
selecting the Private Kubernetes Cluster or providing
Authorized IP Ranges on the Region, Networking
and Security page. 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 Register environment (UI)
documentation.
Using CDP CLI
Run the following command to create the Compute Cluster enabled environment:
cdp environments create-aws-environment
--environment-name [***ENVIRONMENT NAME***] \
--credential-name [***CREDENTIAL NAME***] \
--region [***REGION***] \
--security-access [***SECURITY CONTROL CONFIGURATIONS***] \
--authentication [***PUBLIC SSH KEY***] \
--log-storage [***STORAGE CONFIGURATION***] \
--enable-compute-cluster \
--compute-cluster-configuration \
privateCluster=false, \
kubeApiAuthorizedIpRanges=[***CIDR1***],[***CIDR2***]
workerNodeSubnets=[***SUBNET1***],[***SUBNET2***]
cdp environments create-aws-environment
--environment-name [***ENVIRONMENT NAME***] \
--credential-name [***CREDENTIAL NAME***] \
--region [***REGION***] \
--security-access [***SECURITY CONTROL CONFIGURATIONS***] \
--authentication [***SSH KEY***] \
--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***] ... "awsComputeClusterConfiguration": { "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-aws-compute-cluster
--environment-name [***ENVIRONMENT NAME***] \
--compute-cluster-configuration \
privateCluster=false, \
kubeApiAuthorizedIpRanges=[***CIDR1***],[***CIDR2***]
workerNodeSubnets=[***SUBNET1***],[***SUBNET2***]
cdp environments initialize-aws-compute-cluster
--environment-name [***ENVIRONMENT NAME***] \
--compute-cluster-configuration \
privateCluster=true
workerNodeSubnets=[***SUBNET1***],[***SUBNET2***]