Modify a database cluster

Modifying a database cluster involves adjusting its configuration to align with changing business requirements, optimize performance, or resolve specific operational issues. You might modify a cluster to:

Adjust resource allocation
Update security settings
Modify network parameters
Upgrade versions
Scale up to change a datacenter size or add a new datacenter
Scale down to change a datacenter size or remove a datacenter
Make a configuration change

You can modify a database cluster using the Mission Control UI or CLI. The UI allows you to provision a cluster using simple or expert mode. The UI offers simple mode and expert mode. DataStax recommends simple mode for users who are new to Kubernetes or Mission Control. It allows you to provision a cluster with a few clicks. Expert mode is for users who are familiar with the Kubernetes API and YAML configuration and allows you to define a cluster with more specific settings. DataStax recommends the CLI for users who are familiar with kubectl.

UI simple mode
UI expert mode
CLI

To modify a cluster using simple mode, do the following:

In the Mission Control UI, go to Home, and then click Clusters.
Select the cluster to update.
Click Modify Cluster.
Update the cluster configuration.
Click Modify Cluster to save your changes.

DataStax recommends expert mode only for users who are familiar with the Kubernetes API and YAML configuration.

After you create or update a cluster in expert mode, you cannot edit it in simple mode.

For custom resource definitions (CRDs), see Mission Control Custom Resource Definition (CRD) reference.

To modify a cluster using expert mode, do the following:

In the Mission Control UI, go to Home, and then click Clusters.
Select the cluster to update.
Click Modify Cluster.
Click Expert. The Modify Cluster page displays YAML configuration options.
Edit the YAML configuration to update the cluster.
Click Modify Cluster.

When you use expert mode to copy your YAML definition and create a new cluster on another installation, you must **omit the metadata.resourceVersion property. If you include this property, you can’t make updates to the new cluster with kubectl.

To modify a cluster with the kubectl CLI, do the following:

Edit the cluster manifest.
Apply the changes:
```
kubectl apply -f MANIFEST_FILENAME
```
Replace MANIFEST_FILENAME with the file name of your manifest.

Modify a database cluster

Was this helpful?

Give Feedback