Orchestrate CockroachDB in a Single Kubernetes Cluster

On this page

This page shows you how to orchestrate the deployment, management, and monitoring of a secure 3-node CockroachDB cluster in a single Kubernetes cluster, using the StatefulSet feature directly or via the Helm package manager for Kubernetes.

To deploy across multiple Kubernetes clusters in different geographic regions instead, see Kubernetes Multi-Cluster Deployment. Also, for details about potential performance bottlenecks to be aware of when running CockroachDB in Kubernetes and guidance on how to optimize your deployment for better performance, see CockroachDB Performance on Kubernetes.

Before you begin

Before getting started, it's helpful to review some Kubernetes-specific terminology and current limitations.

Kubernetes terminology

Limitations

Kubernetes version

Kubernetes 1.18 or higher is required in order to use our most up-to-date configuration files. Earlier Kubernetes releases do not support some of the options used in our configuration files. If you need to run on an older version of Kubernetes, we have kept around configuration files that work on older Kubernetes releases in the versioned subdirectories of https://github.com/cockroachdb/cockroach/tree/master/cloud/kubernetes (e.g., v1.7).

Storage

At this time, orchestrations of CockroachDB with Kubernetes use external persistent volumes that are often replicated by the provider. Because CockroachDB already replicates data automatically, this additional layer of replication is unnecessary and can negatively impact performance. High-performance use cases on a private Kubernetes cluster may want to consider using local volumes.

Step 1. Start Kubernetes

Choose whether you want to orchestrate CockroachDB with Kubernetes using the hosted Google Kubernetes Engine (GKE) service or manually on Google Compute Engine (GCE) or AWS. The instructions below will change slightly depending on your choice.

• Hosted GKE
• Manual GCE
• Manual AWS

Hosted GKE

1. Complete the Before You Begin steps described in the Google Kubernetes Engine Quickstart documentation.

   This includes installing gcloud, which is used to create and delete Kubernetes Engine clusters, and kubectl, which is the command-line tool used to manage Kubernetes from your workstation.

   Tip:

   The documentation offers the choice of using Google's Cloud Shell product or using a local shell on your machine. Choose to use a local shell if you want to be able to view the CockroachDB Admin UI using the steps in this guide.

2. From your local workstation, start the Kubernetes cluster:

   $ gcloud container clusters create cockroachdb --machine-type n1-standard-4
   

   Creating cluster cockroachdb...done.
   

   This creates GKE instances and joins them into a single Kubernetes cluster named cockroachdb. The --machine-type flag tells the node pool to use the n1-standard-4 machine type (4 vCPUs, 15 GB memory), which meets our recommended CPU and memory configuration.

   The process can take a few minutes, so do not move on to the next step until you see a Creating cluster cockroachdb...done message and details about your cluster.

3. Get the email address associated with your Google Cloud account:

   $ gcloud info | grep Account
   

   Account: [your.google.cloud.email@example.org]
   

   Warning:

   This command returns your email address in all lowercase. However, in the next step, you must enter the address using the accurate capitalization. For example, if your address is YourName@example.com, you must use YourName@example.com and not yourname@example.com.

4. Create the RBAC roles CockroachDB needs for running on GKE, using the address from the previous step:

   $ kubectl create clusterrolebinding $USER-cluster-admin-binding --clusterrole=cluster-admin --user=<your.google.cloud.email@example.org>
   

   clusterrolebinding "cluster-admin-binding" created
   

Manual GCE

From your local workstation, install prerequisites and start a Kubernetes cluster as described in the Running Kubernetes on Google Compute Engine documentation.

The process includes:

• Creating a Google Cloud Platform account, installing gcloud, and other prerequisites.
• Downloading and installing the latest Kubernetes release.
• Creating GCE instances and joining them into a single Kubernetes cluster.
• Installing kubectl, the command-line tool used to manage Kubernetes from your workstation.

Manual AWS

From your local workstation, install prerequisites and start a Kubernetes cluster as described in the Running Kubernetes on AWS EC2 documentation.

Step 2. Start CockroachDB

To start your CockroachDB cluster, you can either use our StatefulSet configuration and related files directly, or you can use the Helm package manager for Kubernetes to simplify the process.

Step 3. Use the built-in SQL client

To use the built-in SQL client, you need to launch a pod that runs indefinitely with the cockroach binary inside it, get a shell into the pod, and then start the built-in SQL client.

Step 4. Access the Admin UI

To access the cluster's Admin UI:

1. Port-forward from your local machine to one of the pods:

   $ kubectl port-forward cockroachdb-0 8080
   

   $ kubectl port-forward my-release-cockroachdb-0 8080
   

   Forwarding from 127.0.0.1:8080 -> 8080
   

   Note:

   The port-forward command must be run on the same machine as the web browser in which you want to view the Admin UI. If you have been running these commands from a cloud instance or other non-local shell, you will not be able to view the UI without configuring kubectl locally and running the above port-forward command on your local machine.

2. Go to https://localhost:8080 and log in with the username and password you created earlier.

3. In the UI, verify that the cluster is running as expected:

   • Click View nodes list on the right to ensure that all nodes successfully joined the cluster.
   • Click the Databases tab on the left to verify that bank is listed.

Step 5. Simulate node failure

Based on the replicas: 3 line in the StatefulSet configuration, Kubernetes ensures that three pods/nodes are running at all times. When a pod/node fails, Kubernetes automatically creates another pod/node with the same network identity and persistent storage.

To see this in action:

1. Terminate one of the CockroachDB nodes:

   $ kubectl delete pod cockroachdb-2
   

   pod "cockroachdb-2" deleted
   

   $ kubectl delete pod my-release-cockroachdb-2
   

   pod "my-release-cockroachdb-2" deleted
   

2. In the Admin UI, the Cluster Overview will soon show one node as Suspect. As Kubernetes auto-restarts the node, watch how the node once again becomes healthy.

3. Back in the terminal, verify that the pod was automatically restarted:

   $ kubectl get pod cockroachdb-2
   

   NAME            READY     STATUS    RESTARTS   AGE
   cockroachdb-2   1/1       Running   0          12s
   

   $ kubectl get pod my-release-cockroachdb-2
   

   NAME                       READY     STATUS    RESTARTS   AGE
   my-release-cockroachdb-2   1/1       Running   0          44s
   

Step 6. Set up monitoring and alerting

Despite CockroachDB's various built-in safeguards against failure, it is critical to actively monitor the overall health and performance of a cluster running in production and to create alerting rules that promptly send notifications when there are events that require investigation or intervention.

Configure Prometheus

Every node of a CockroachDB cluster exports granular timeseries metrics formatted for easy integration with Prometheus, an open source tool for storing, aggregating, and querying timeseries data. This section shows you how to orchestrate Prometheus as part of your Kubernetes cluster and pull these metrics into Prometheus for external monitoring.

This guidance is based on CoreOS's Prometheus Operator, which allows a Prometheus instance to be managed using built-in Kubernetes concepts.

1. From your local workstation, edit the cockroachdb service to add the prometheus: cockroachdb label:

   $ kubectl label svc cockroachdb prometheus=cockroachdb
   

   service "cockroachdb" labeled
   

   This ensures that there is a prometheus job and monitoring data only for the cockroachdb service, not for the cockroach-public service.

   $ kubectl label svc my-release-cockroachdb prometheus=cockroachdb
   

   service "cockroachdb" labeled
   

   This ensures that there is a prometheus job and monitoring data only for the my-release-cockroachdb service, not for the my-release-cockroach-public service.

2. Install CoreOS's Prometheus Operator:

   $ kubectl apply -f https://raw.githubusercontent.com/coreos/prometheus-operator/release-0.20/bundle.yaml
   

   clusterrolebinding "prometheus-operator" created
   clusterrole "prometheus-operator" created
   serviceaccount "prometheus-operator" created
   deployment "prometheus-operator" created
   

3. Confirm that the prometheus-operator has started:

   $ kubectl get deploy prometheus-operator
   

   NAME                  DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
   prometheus-operator   1         1         1            1           1m
   

4. Use our prometheus.yaml file to create the various objects necessary to run a Prometheus instance:

   $ kubectl apply -f https://raw.githubusercontent.com/cockroachdb/cockroach/master/cloud/kubernetes/prometheus/prometheus.yaml
   

   clusterrole "prometheus" created
   clusterrolebinding "prometheus" created
   servicemonitor "cockroachdb" created
   prometheus "cockroachdb" created
   

5. Access the Prometheus UI locally and verify that CockroachDB is feeding data into Prometheus:

   1. Port-forward from your local machine to the pod running Prometheus:

      $ kubectl port-forward prometheus-cockroachdb-0 9090
      

   2. Go to http://localhost:9090 in your browser.

   3. To verify that each CockroachDB node is connected to Prometheus, go to Status > Targets. The screen should look like this:

      

   4. To verify that data is being collected, go to Graph, enter the sys_uptime variable in the field, click Execute, and then click the Graph tab. The screen should like this:

      

   Tip:

   Prometheus auto-completes CockroachDB time series metrics for you, but if you want to see a full listing, with descriptions, port-forward as described in Access the Admin UI and then point your browser to http://localhost:8080/_status/vars.

   For more details on using the Prometheus UI, see their official documentation.

Configure Alertmanager

Active monitoring helps you spot problems early, but it is also essential to send notifications when there are events that require investigation or intervention. This section shows you how to use Alertmanager and CockroachDB's starter alerting rules to do this.

1. Download our alertmanager-config.yaml configuration file.

2. Edit the alertmanager-config.yaml file to specify the desired receivers for notifications. Initially, the file contains a placeholder web hook.

3. Add this configuration to the Kubernetes cluster as a secret, renaming it to alertmanager.yaml and labelling it to make it easier to find:

   $ kubectl create secret generic alertmanager-cockroachdb --from-file=alertmanager.yaml=alertmanager-config.yaml
   

   secret "alertmanager-cockroachdb" created
   

   $ kubectl label secret alertmanager-cockroachdb app=cockroachdb
   

   secret "alertmanager-cockroachdb" labeled
   

   Warning:

   The name of the secret, alertmanager-cockroachdb, must match the name used in the altermanager.yaml file. If they differ, the Alertmanager instance will start without configuration, and nothing will happen.

4. Use our alertmanager.yaml file to create the various objects necessary to run an Alertmanager instance, including a ClusterIP service so that Prometheus can forward alerts:

   $ kubectl apply -f https://raw.githubusercontent.com/cockroachdb/cockroach/master/cloud/kubernetes/prometheus/alertmanager.yaml
   

   alertmanager "cockroachdb" created
   service "alertmanager-cockroachdb" created
   

5. Verify that Alertmanager is running:

   1. Port-forward from your local machine to the pod running Alertmanager:

      $ kubectl port-forward alertmanager-cockroachdb-0 9093
      

   2. Go to http://localhost:9093 in your browser. The screen should look like this:

      

6. Ensure that the Alertmanagers are visible to Prometheus by opening http://localhost:9090/status. The screen should look like this:

   

7. Add CockroachDB's starter alerting rules:

   $ kubectl apply -f https://raw.githubusercontent.com/cockroachdb/cockroach/master/cloud/kubernetes/prometheus/alert-rules.yaml
   

   prometheusrule "prometheus-cockroachdb-rules" created
   

8. Ensure that the rules are visible to Prometheus by opening http://localhost:9090/rules. The screen should look like this:

   

9. Verify that the example alert is firing by opening http://localhost:9090/alerts. The screen should look like this:

   

10. To remove the example alert:

    1. Use the kubectl edit command to open the rules for editing:

       $ kubectl edit prometheusrules prometheus-cockroachdb-rules
       

    2. Remove the dummy.rules block and save the file:

       - name: rules/dummy.rules
         rules:
         - alert: TestAlertManager
           expr: vector(1)
       

Step 7. Maintain the cluster

Add nodes

The Kubernetes cluster contains 4 nodes, one master and 3 workers. Pods get placed only on worker nodes, so to ensure that you do not have two pods on the same node (as recommended in our production best practices), you need to add a new worker node and then edit your StatefulSet configuration to add another pod. The Kubernetes cluster we created contains 3 nodes that pods can be run on. To ensure that you do not have two pods on the same node (as recommended in our production best practices), you need to add a new node and then edit your StatefulSet configuration to add another pod.

1. Add a worker node:

   • On GKE, resize your cluster.
   • On GCE, resize your Managed Instance Group.
   • On AWS, resize your Auto Scaling Group.

2. Use the kubectl scale command to add a pod to your StatefulSet:

   $ kubectl scale statefulset cockroachdb --replicas=4
   

   statefulset "cockroachdb" scaled
   

   $ kubectl scale statefulset my-release-cockroachdb --replicas=4
   

   statefulset "my-release-cockroachdb" scaled
   

3. Get the name of the Pending CSR for the new pod:

   $ kubectl get csr
   

   NAME                                                   AGE       REQUESTOR                               CONDITION
   default.client.root                                    1h        system:serviceaccount:default:default   Approved,Issued
   default.node.cockroachdb-0                             1h        system:serviceaccount:default:default   Approved,Issued
   default.node.cockroachdb-1                             1h        system:serviceaccount:default:default   Approved,Issued
   default.node.cockroachdb-2                             1h        system:serviceaccount:default:default   Approved,Issued
   default.node.cockroachdb-3                             2m        system:serviceaccount:default:default   Pending
   node-csr-0Xmb4UTVAWMEnUeGbW4KX1oL4XV_LADpkwjrPtQjlZ4   1h        kubelet                                 Approved,Issued
   node-csr-NiN8oDsLhxn0uwLTWa0RWpMUgJYnwcFxB984mwjjYsY   1h        kubelet                                 Approved,Issued
   node-csr-aU78SxyU69pDK57aj6txnevr7X-8M3XgX9mTK0Hso6o   1h        kubelet                                 Approved,Issued
   

   If you do not see a Pending CSR, wait a minute and try again.

4. Examine the CSR for the new pod:

   $ kubectl describe csr default.node.cockroachdb-3
   

   Name:               default.node.cockroachdb-0
   Labels:             <none>
   Annotations:        <none>
   CreationTimestamp:  Thu, 09 Nov 2017 13:39:37 -0500
   Requesting User:    system:serviceaccount:default:default
   Status:             Pending
   Subject:
     Common Name:    node
     Serial Number:
     Organization:   Cockroach
   Subject Alternative Names:
            DNS Names:     localhost
                           cockroachdb-0.cockroachdb.default.svc.cluster.local
                           cockroachdb-public
            IP Addresses:  127.0.0.1
                           10.48.1.6
   Events:  <none>
   

5. If everything looks correct, approve the CSR for the new pod:

   $ kubectl certificate approve default.node.cockroachdb-3
   

   certificatesigningrequest "default.node.cockroachdb-3" approved
   

6. Verify that the new pod started successfully:

   $ kubectl get pods
   

   NAME                        READY     STATUS    RESTARTS   AGE
   cockroachdb-0               1/1       Running   0          51m
   cockroachdb-1               1/1       Running   0          47m
   cockroachdb-2               1/1       Running   0          3m
   cockroachdb-3               1/1       Running   0          1m
   cockroachdb-client-secure   1/1       Running   0          15m
   

7. Back in the Admin UI, view Node List to ensure that the fourth node successfully joined the cluster.

Remove nodes

To safely remove a node from your cluster, you must first decommission the node and only then adjust the --replicas value of your StatefulSet configuration to permanently remove it. This sequence is important because the decommissioning process lets a node finish in-flight requests, rejects any new requests, and transfers all range replicas and range leases off the node.

1. Get a shell into the cockroachdb-client-secure pod you created earlier and use the cockroach node status command to get the internal IDs of nodes:

   $ kubectl exec -it cockroachdb-client-secure -- ./cockroach node status --certs-dir=/cockroach-certs --host=cockroachdb-public
   

     id |               address                                     | build  |            started_at            |            updated_at            | is_available | is_live
   +----+---------------------------------------------------------------------------------+--------+----------------------------------+----------------------------------+--------------+---------+
      1 | cockroachdb-0.cockroachdb.default.svc.cluster.local:26257 | v2.1.1 | 2018-11-29 16:04:36.486082+00:00 | 2018-11-29 18:24:24.587454+00:00 | true         | true
      2 | cockroachdb-2.cockroachdb.default.svc.cluster.local:26257 | v2.1.1 | 2018-11-29 16:55:03.880406+00:00 | 2018-11-29 18:24:23.469302+00:00 | true         | true
      3 | cockroachdb-1.cockroachdb.default.svc.cluster.local:26257 | v2.1.1 | 2018-11-29 16:04:41.383588+00:00 | 2018-11-29 18:24:25.030175+00:00 | true         | true
      4 | cockroachdb-3.cockroachdb.default.svc.cluster.local:26257 | v2.1.1 | 2018-11-29 17:31:19.990784+00:00 | 2018-11-29 18:24:26.041686+00:00 | true         | true
   (4 rows)
   

   $ kubectl exec -it cockroachdb-client-secure -- ./cockroach node status --certs-dir=/cockroach-certs --host=my-release-cockroachdb-public
   

     id |                                     address                                     | build  |            started_at            |            updated_at            | is_available | is_live
   +----+---------------------------------------------------------------------------------+--------+----------------------------------+----------------------------------+--------------+---------+
      1 | my-release-cockroachdb-0.my-release-cockroachdb.default.svc.cluster.local:26257 | v2.1.1 | 2018-11-29 16:04:36.486082+00:00 | 2018-11-29 18:24:24.587454+00:00 | true         | true
      2 | my-release-cockroachdb-2.my-release-cockroachdb.default.svc.cluster.local:26257 | v2.1.1 | 2018-11-29 16:55:03.880406+00:00 | 2018-11-29 18:24:23.469302+00:00 | true         | true
      3 | my-release-cockroachdb-1.my-release-cockroachdb.default.svc.cluster.local:26257 | v2.1.1 | 2018-11-29 16:04:41.383588+00:00 | 2018-11-29 18:24:25.030175+00:00 | true         | true
      4 | my-release-cockroachdb-3.my-release-cockroachdb.default.svc.cluster.local:26257 | v2.1.1 | 2018-11-29 17:31:19.990784+00:00 | 2018-11-29 18:24:26.041686+00:00 | true         | true
   (4 rows)
   

   The pod uses the root client certificate created earlier to initialize the cluster, so there's no CSR approval required.

2. Note the ID of the node with the highest number in its address (in this case, the address including cockroachdb-3) and use the cockroach node decommission command to decommission it:

   Note:

   It's important to decommission the node with the highest number in its address because, when you reduce the --replica count, Kubernetes will remove the pod for that node.

   $ kubectl exec -it cockroachdb-client-secure -- ./cockroach node decommission <node ID> --insecure --host=cockroachdb-public
   

   $ kubectl exec -it cockroachdb-client-secure -- ./cockroach node decommission <node ID> --insecure --host=my-release-cockroachdb-public
   

   You'll then see the decommissioning status print to stderr as it changes:

    id | is_live | replicas | is_decommissioning | is_draining  
   +---+---------+----------+--------------------+-------------+
     4 |  true   |       73 |        true        |    false     
   (1 row)
   

   Once the node has been fully decommissioned and stopped, you'll see a confirmation:

    id | is_live | replicas | is_decommissioning | is_draining  
   +---+---------+----------+--------------------+-------------+
     4 |  true   |        0 |        true        |    false     
   (1 row)
   
   No more data reported on target nodes. Please verify cluster health before removing the nodes.
   

3. Once the node has been decommissioned, use the kubectl scale command to remove a pod from your StatefulSet:

   $ kubectl scale statefulset cockroachdb --replicas=3
   

   statefulset "cockroachdb" scaled
   

   $ kubectl scale statefulset my-release-cockroachdb --replicas=3
   

   statefulset "my-release-cockroachdb" scaled
   

Upgrade the cluster

As new versions of CockroachDB are released, it's strongly recommended to upgrade to newer versions in order to pick up bug fixes, performance improvements, and new features. The general CockroachDB upgrade documentation provides best practices for how to prepare for and execute upgrades of CockroachDB clusters, but the mechanism of actually stopping and restarting processes in Kubernetes is somewhat special.

Kubernetes knows how to carry out a safe rolling upgrade process of the CockroachDB nodes. When you tell it to change the Docker image used in the CockroachDB StatefulSet, Kubernetes will go one-by-one, stopping a node, restarting it with the new image, and waiting for it to be ready to receive client requests before moving on to the next one. For more information, see the Kubernetes documentation.

1. Decide how the upgrade will be finalized.

   Note:

   This step is relevant only when upgrading from v2.0.x to v2.1. For upgrades within the v2.1.x series, skip this step.

   By default, after all nodes are running the new version, the upgrade process will be auto-finalized. This will enable certain performance improvements and bug fixes introduced in v2.1. After finalization, however, it will no longer be possible to perform a downgrade to v2.0. In the event of a catastrophic failure or corruption, the only option will be to start a new cluster using the old binary and then restore from one of the backups created prior to performing the upgrade.

   We recommend disabling auto-finalization so you can monitor the stability and performance of the upgraded cluster before finalizing the upgrade:

   1. Get a shell into the pod with the cockroach binary created earlier and start the CockroachDB built-in SQL client:

      $ kubectl exec -it cockroachdb-client-secure -- ./cockroach sql --certs-dir=/cockroach-certs --host=cockroachdb-public
      

      $ kubectl exec -it cockroachdb-client-secure -- ./cockroach sql --certs-dir=/cockroach-certs --host=my-release-cockroachdb-public
      

   2. Set the cluster.preserve_downgrade_option cluster setting:

      > SET CLUSTER SETTING cluster.preserve_downgrade_option = '2.0';
      

2. Kick off the upgrade process by changing the desired Docker image. To do so, pick the version that you want to upgrade to, then run the following command, replacing "VERSION" with your desired new version:

   $ kubectl patch statefulset cockroachdb --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/image", "value":"cockroachdb/cockroach:VERSION"}]'
   

   statefulset "cockroachdb" patched
   

   $ kubectl patch statefulset my-release-cockroachdb --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/image", "value":"cockroachdb/cockroach:VERSION"}]'
   

   statefulset "my-release0-cockroachdb" patched
   

3. If you then check the status of your cluster's pods, you should see one of them being restarted:

   $ kubectl get pods
   

   NAME            READY     STATUS        RESTARTS   AGE
   cockroachdb-0   1/1       Running       0          2m
   cockroachdb-1   1/1       Running       0          2m
   cockroachdb-2   1/1       Running       0          2m
   cockroachdb-3   0/1       Terminating   0          1m
   

   NAME                       READY     STATUS        RESTARTS   AGE
   my-release-cockroachdb-0   1/1       Running       0          2m
   my-release-cockroachdb-1   1/1       Running       0          2m
   my-release-cockroachdb-2   1/1       Running       0          2m
   my-release-cockroachdb-3   0/1       Terminating   0          1m
   

4. This will continue until all of the pods have restarted and are running the new image. To check the image of each pod to determine whether they've all be upgraded, run:

   $ kubectl get pods -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.spec.containers[0].image}{"\n"}'
   

   cockroachdb-0   cockroachdb/cockroach:v2.1.11
   cockroachdb-1   cockroachdb/cockroach:v2.1.11
   cockroachdb-2   cockroachdb/cockroach:v2.1.11
   cockroachdb-3   cockroachdb/cockroach:v2.1.11
   

   my-release-cockroachdb-0    cockroachdb/cockroach:v2.1.11
   my-release-cockroachdb-1    cockroachdb/cockroach:v2.1.11
   my-release-cockroachdb-2    cockroachdb/cockroach:v2.1.11
   my-release-cockroachdb-3    cockroachdb/cockroach:v2.1.11
   

5. Finish the upgrade.

   Note:

   This step is relevant only when upgrading from v2.0.x to v2.1. For upgrades within the v2.1.x series, skip this step.

   If you disabled auto-finalization in step 1 above, monitor the stability and performance of your cluster for as long as you require to feel comfortable with the upgrade (generally at least a day). If during this time you decide to roll back the upgrade, repeat the rolling restart procedure with the old binary.

   Once you are satisfied with the new version, re-enable auto-finalization:

   1. Get a shell into the pod with the cockroach binary created earlier and start the CockroachDB built-in SQL client:

      $ kubectl exec -it cockroachdb-client-secure -- ./cockroach sql --certs-dir=/cockroach-certs --host=cockroachdb-public
      

      $ kubectl exec -it cockroachdb-client-secure -- ./cockroach sql --certs-dir=/cockroach-certs --host=my-release-cockroachdb-public
      

   2. Re-enable auto-finalization:

      > RESET CLUSTER SETTING cluster.preserve_downgrade_option;
      

Stop the cluster

To shut down the CockroachDB cluster:

1. Delete all of the resources associated with the cockroachdb label, including the logs, remote persistent volumes, and Prometheus and Alertmanager resources:

   $ kubectl delete pods,statefulsets,services,persistentvolumeclaims,persistentvolumes,poddisruptionbudget,jobs,rolebinding,clusterrolebinding,role,clusterrole,serviceaccount,alertmanager,prometheus,prometheusrule,serviceMonitor -l app=cockroachdb
   

   pod "cockroachdb-0" deleted
   pod "cockroachdb-1" deleted
   pod "cockroachdb-2" deleted
   service "alertmanager-cockroachdb" deleted
   service "cockroachdb" deleted
   service "cockroachdb-public" deleted
   persistentvolumeclaim "datadir-cockroachdb-0" deleted
   persistentvolumeclaim "datadir-cockroachdb-1" deleted
   persistentvolumeclaim "datadir-cockroachdb-2" deleted
   poddisruptionbudget "cockroachdb-budget" deleted
   job "cluster-init-secure" deleted
   rolebinding "cockroachdb" deleted
   clusterrolebinding "cockroachdb" deleted
   clusterrolebinding "prometheus" deleted
   role "cockroachdb" deleted
   clusterrole "cockroachdb" deleted
   clusterrole "prometheus" deleted
   serviceaccount "cockroachdb" deleted
   serviceaccount "prometheus" deleted
   alertmanager "cockroachdb" deleted
   prometheus "cockroachdb" deleted
   prometheusrule "prometheus-cockroachdb-rules" deleted
   servicemonitor "cockroachdb" deleted
   

2. Delete the pod created for cockroach client commands, if you didn't do so earlier:

   $ kubectl delete pod cockroachdb-client-secure
   

   pod "cockroachdb-client-secure" deleted
   

3. Get the names of the CSRs for the cluster:

   $ kubectl get csr
   

   NAME                                                   AGE       REQUESTOR                               CONDITION
   default.client.root                                    1h        system:serviceaccount:default:default   Approved,Issued
   default.node.cockroachdb-0                             1h        system:serviceaccount:default:default   Approved,Issued
   default.node.cockroachdb-1                             1h        system:serviceaccount:default:default   Approved,Issued
   default.node.cockroachdb-2                             1h        system:serviceaccount:default:default   Approved,Issued
   default.node.cockroachdb-3                             12m       system:serviceaccount:default:default   Approved,Issued
   node-csr-0Xmb4UTVAWMEnUeGbW4KX1oL4XV_LADpkwjrPtQjlZ4   1h        kubelet                                 Approved,Issued
   node-csr-NiN8oDsLhxn0uwLTWa0RWpMUgJYnwcFxB984mwjjYsY   1h        kubelet                                 Approved,Issued
   node-csr-aU78SxyU69pDK57aj6txnevr7X-8M3XgX9mTK0Hso6o   1h        kubelet                                 Approved,Issued
   

4. Delete the CSRs that you created:

   $ kubectl delete csr default.client.root default.node.cockroachdb-0 default.node.cockroachdb-1 default.node.cockroachdb-2 default.node.cockroachdb-3
   

   certificatesigningrequest "default.client.root" deleted
   certificatesigningrequest "default.node.cockroachdb-0" deleted
   certificatesigningrequest "default.node.cockroachdb-1" deleted
   certificatesigningrequest "default.node.cockroachdb-2" deleted
   certificatesigningrequest "default.node.cockroachdb-3" deleted
   

5. Get the names of the secrets for the cluster:

   $ kubectl get secrets
   

   NAME                         TYPE                                  DATA      AGE
   alertmanager-cockroachdb          Opaque                                1         1h
   default-token-d9gff               kubernetes.io/service-account-token   3         5h
   default.client.root               Opaque                                2         5h
   default.node.cockroachdb-0        Opaque                                2         5h
   default.node.cockroachdb-1        Opaque                                2         5h
   default.node.cockroachdb-2        Opaque                                2         5h
   default.node.cockroachdb-3        Opaque                                2         5h
   prometheus-operator-token-bpdv8   kubernetes.io/service-account-token   3         3h
   

6. Delete the secrets that you created:

   $ kubectl delete secrets alertmanager-cockroachdb default.client.root default.node.cockroachdb-0 default.node.cockroachdb-1 default.node.cockroachdb-2 default.node.cockroachdb-3
   

   secret "alertmanager-cockroachdb" deleted
   secret "default.client.root" deleted
   secret "default.node.cockroachdb-0" deleted
   secret "default.node.cockroachdb-1" deleted
   secret "default.node.cockroachdb-2" deleted
   secret "default.node.cockroachdb-3" deleted
   

7. Stop Kubernetes:

   • Hosted GKE:

     $ gcloud container clusters delete cockroachdb
     

   • Manual GCE:

     $ cluster/kube-down.sh
     

   • Manual AWS:

     $ cluster/kube-down.sh
     

   Warning:

   If you stop Kubernetes without first deleting the persistent volumes, they will still exist in your cloud project.

See also

• Kubernetes Multi-Cluster Deployment
• Kubernetes Performance Guide
• Production Checklist
• Manual Deployment
• Orchestrated Deployment
• Monitoring and Alerting
• Performance Benchmarking
• Performance Tuning
• Local Deployment

Was this helpful?