CockroachDB - the open source, cloud-native distributed SQL database.
Below is a brief overview of operating the CockroachDB Helm Chart and some specific implementation details. For additional information on deploying CockroachDB, please see:
https://www.cockroachlabs.com/docs/stable/orchestrate-cockroachdb-with-kubernetes.html
Note that the documentation requires Helm 3.0 or higher.
- Kubernetes 1.8
- PV support on the underlying infrastructure (only if using
storage.persistentVolume). Docker for windows hostpath provisioner is not supported. - If you want to secure your cluster to use TLS certificates for all network communication, Helm must be installed with RBAC privileges or else you will get an "attempt to grant extra privileges" error.
This chart will do the following:
- Set up a dynamically scalable CockroachDB cluster using a Kubernetes StatefulSet.
helm repo add cockroachdb https://charts.cockroachdb.com/To install the chart with the release name my-release:
helm install my-release cockroachdb/cockroachdbNote that for a production cluster, you will likely want to override the following parameters in values.yaml with your own values.
statefulset.resources.requests.memoryandstatefulset.resources.limits.memoryallocate memory resources to CockroachDB pods in your cluster.conf.cacheandconf.max-sql-memoryare memory limits that we recommend setting to 1/4 of the above resource allocation. When running CockroachDB, you must set these limits explicitly to avoid running out of memory.storage.persistentVolume.sizedefaults to100Giof disk space per pod, which you may increase or decrease for your use case.storage.persistentVolume.storageClassuses the default storage class for your environment. We strongly recommend that you specify a storage class which uses an SSD.tls.enabledmust be set toyes/trueto deploy in secure mode.
For more information on overriding the values.yaml parameters, please see:
Confirm that all pods are Running successfully and init has been completed:
kubectl get podsNAME READY STATUS RESTARTS AGE
my-release-cockroachdb-0 1/1 Running 0 1m
my-release-cockroachdb-1 1/1 Running 0 1m
my-release-cockroachdb-2 1/1 Running 0 1m
my-release-cockroachdb-init-k6jcr 0/1 Completed 0 1m
Confirm that persistent volumes are created and claimed for each pod:
kubectl get pvNAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
pvc-64878ebf-f3f0-11e8-ab5b-42010a8e0035 100Gi RWO Delete Bound default/datadir-my-release-cockroachdb-0 standard 51s
pvc-64945b4f-f3f0-11e8-ab5b-42010a8e0035 100Gi RWO Delete Bound default/datadir-my-release-cockroachdb-1 standard 51s
pvc-649d920d-f3f0-11e8-ab5b-42010a8e0035 100Gi RWO Delete Bound default/datadir-my-release-cockroachdb-2 standard 51s
In order to set up a secure cockroachdb cluster set tls.enabled to yes/true
There are 3 ways to configure a secure cluster, with this chart. This all relates to how the certificates are issued:
- Self-signer (default)
- Cert-manager
- Manual
This is the default behaviour, and requires no configuration beyond setting certificate durations if user wants to set custom duration.
If you are running in this mode, self-signed certificates are created by self-signed utility for the nodes and root client and are stored in a secret. You can look for the certificates created:
kubectl get secretscrdb-cockroachdb-ca-secret Opaque 2 23s
crdb-cockroachdb-client-secret kubernetes.io/tls 3 22s
crdb-cockroachdb-node-secret kubernetes.io/tls 3 23sIf you wish to supply the certificates to the nodes yourself set tls.certs.provided to yes/true. You may want to use this if you want to use a different certificate authority from the one being used by Kubernetes or if your Kubernetes cluster doesn't fully support certificate-signing requests. To use this, first set up your certificates and load them into your Kubernetes cluster as Secrets using the commands below:
$ mkdir certs
$ mkdir my-safe-directory
$ cockroach cert create-ca --certs-dir=certs --ca-key=my-safe-directory/ca.key
$ cockroach cert create-client root --certs-dir=certs --ca-key=my-safe-directory/ca.key
$ kubectl create secret generic cockroachdb-root --from-file=certs
secret/cockroachdb-root created
$ cockroach cert create-node --certs-dir=certs --ca-key=my-safe-directory/ca.key localhost 127.0.0.1 my-release-cockroachdb-public my-release-cockroachdb-public.my-namespace my-release-cockroachdb-public.my-namespace.svc.cluster.local *.my-release-cockroachdb *.my-release-cockroachdb.my-namespace *.my-release-cockroachdb.my-namespace.svc.cluster.local
$ kubectl create secret generic cockroachdb-node --from-file=certs
secret/cockroachdb-node createdNote: The subject alternative names are based on a release called
my-releasein themy-namespacenamespace. Make sure they match the services created with the release duringhelm install
If your certificates are stored in tls secrets such as secrets generated by cert-manager, the secret will contain files named:
ca.crttls.crttls.key
Cockroachdb, however, expects the files to be named like this:
ca.crtnode.crtnode.keyclient.root.crtclient.root.key
By enabling tls.certs.tlsSecret the tls secrets are projected on to the correct filenames, when they are mounted to the cockroachdb pods.
If you wish to supply certificates with cert-manager, set
tls.certs.certManagertoyes/truetls.certs.certManagerIssuerto an IssuerRef (as they appear in certificate resources) pointing to a clusterIssuer or issuer, you have set up in the cluster
Example issuer:
apiVersion: v1
kind: Secret
metadata:
name: cockroachdb-ca
namespace: cockroachdb
data:
tls.crt: [BASE64 Encoded ca.crt]
tls.key: [BASE64 Encoded ca.key]
type: kubernetes.io/tls
---
apiVersion: cert-manager.io/v1alpha3
kind: Issuer
metadata:
name: cockroachdb-cert-issuer
namespace: cockroachdb
spec:
ca:
secretName: cockroachdb-caLaunch a temporary interactive pod and start the built-in SQL client:
kubectl run cockroachdb --rm -it \
--image=cockroachdb/cockroach \
--restart=Never \
-- sql --insecure --host=my-release-cockroachdb-publicIf you are running in secure mode, you will have to provide a client certificate to the cluster in order to authenticate, so the above command will not work. See here for an example of how to set up an interactive SQL shell against a secure cluster or here for an example application connecting to a secure cluster.
Set cluster.preserve_downgrade_option, where $current_version is the CockroachDB version currently running (e.g., 19.2):
> SET CLUSTER SETTING cluster.preserve_downgrade_option = '$current_version';Exit the shell and delete the temporary pod:
> \qKick off the upgrade process by changing the new Docker image, where $new_version is the CockroachDB version to which you are upgrading:
helm upgrade my-release cockroachdb/cockroachdb \
--set image.tag=$new_version \
--reuse-valuesKubernetes will carry out a safe rolling upgrade of your CockroachDB nodes one-by-one. Monitor the cluster's pods until all have been successfully restarted:
kubectl get podsNAME READY STATUS RESTARTS AGE
my-release-cockroachdb-0 1/1 Running 0 2m
my-release-cockroachdb-1 1/1 Running 0 3m
my-release-cockroachdb-2 1/1 Running 0 3m
my-release-cockroachdb-3 0/1 ContainerCreating 0 25s
my-release-cockroachdb-init-nwjkh 0/1 ContainerCreating 0 6s
kubectl get pods \
-o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.spec.containers[0].image}{"\n"}'my-release-cockroachdb-0 cockroachdb/cockroach:v23.1.7
my-release-cockroachdb-1 cockroachdb/cockroach:v23.1.7
my-release-cockroachdb-2 cockroachdb/cockroach:v23.1.7
my-release-cockroachdb-3 cockroachdb/cockroach:v23.1.7
Resume normal operations. Once you are comfortable that the stability and performance of the cluster is what you'd expect post-upgrade, finalize the upgrade:
kubectl run cockroachdb --rm -it \
--image=cockroachdb/cockroach \
--restart=Never \
-- sql --insecure --host=my-release-cockroachdb-public> RESET CLUSTER SETTING cluster.preserve_downgrade_option;
> \qDue to a change in the label format in version 3.0.0 of this chart, upgrading requires that you delete the StatefulSet. Luckily there is a way to do it without actually deleting all the resources managed by the StatefulSet. Use the workaround below to upgrade from charts versions previous to 3.0.0:
Get the new labels from the specs rendered by Helm:
helm template -f deploy.vals.yml cockroachdb/cockroachdb -x templates/statefulset.yaml \
| yq r - spec.template.metadata.labelsapp.kubernetes.io/name: cockroachdb
app.kubernetes.io/instance: my-release
app.kubernetes.io/component: cockroachdb
Place the new labels on all pods of the StatefulSet (change my-release-cockroachdb-0 to the name of each pod):
kubectl label pods my-release-cockroachdb-0 \
app.kubernetes.io/name=cockroachdb \
app.kubernetes.io/instance=my-release \
app.kubernetes.io/component=cockroachdbDelete the StatefulSet without deleting pods:
kubectl delete statefulset my-release-cockroachdb --cascade=falseVerify that no pod is deleted and then upgrade as normal. A new StatefulSet will be created, taking over the management of the existing pods and upgrading them if needed.
For more information about upgrading a cluster to the latest major release of CockroachDB, see Upgrade to CockroachDB.
Note that there are sometimes backward-incompatible changes to SQL features between major CockroachDB releases. For details, see the Upgrade Policy.
The following table lists the configurable parameters of the CockroachDB chart and their default values.
For details see the values.yaml file.
| Parameter | Description | Default |
|---|---|---|
clusterDomain |
Cluster's default DNS domain | cluster.local |
conf.attrs |
CockroachDB node attributes | [] |
conf.cache |
Size of CockroachDB's in-memory cache | 25% |
conf.cluster-name |
Name of CockroachDB cluster | "" |
conf.disable-cluster-name-verification |
Disable CockroachDB cluster name verification | no |
conf.join |
List of already-existing CockroachDB instances | [] |
conf.max-disk-temp-storage |
Max storage capacity for temp data | 0 |
conf.max-offset |
Max allowed clock offset for CockroachDB cluster | 500ms |
conf.max-sql-memory |
Max memory to use processing SQL querie | 25% |
conf.locality |
Locality attribute for this deployment | "" |
conf.single-node |
Disable CockroachDB clustering (standalone mode) | no |
conf.sql-audit-dir |
Directory for SQL audit log | "" |
conf.port |
CockroachDB primary serving port in Pods | 26257 |
conf.http-port |
CockroachDB HTTP port in Pods | 8080 |
conf.path |
CockroachDB data directory mount path | cockroach-data |
conf.store.enabled |
Enable store configuration for CockroachDB | false |
conf.store.type |
CockroachDB storage type | "" |
conf.store.size |
CockroachDB storage size | "" |
conf.store.attrs |
CockroachDB storage attributes | "" |
image.repository |
Container image name | cockroachdb/cockroach |
image.tag |
Container image tag | v23.1.7 |
image.pullPolicy |
Container pull policy | IfNotPresent |
image.credentials |
registry, user and pass credentials to pull private image |
{} |
statefulset.replicas |
StatefulSet replicas number | 3 |
statefulset.updateStrategy |
Update strategy for StatefulSet Pods | {"type": "RollingUpdate"} |
statefulset.podManagementPolicy |
OrderedReady/Parallel Pods creation/deletion order |
Parallel |
statefulset.budget.maxUnavailable |
k8s PodDisruptionBudget parameter | 1 |
statefulset.args |
Extra command-line arguments | [] |
statefulset.env |
Extra env vars | [] |
statefulset.secretMounts |
Additional Secrets to mount at cluster members | [] |
statefulset.labels |
Additional labels of StatefulSet and its Pods | {"app.kubernetes.io/component": "cockroachdb"} |
statefulset.annotations |
Additional annotations of StatefulSet Pods | {} |
statefulset.nodeAffinity |
Node affinity rules of StatefulSet Pods | {} |
statefulset.podAffinity |
Inter-Pod affinity rules of StatefulSet Pods | {} |
statefulset.podAntiAffinity |
Anti-affinity rules of StatefulSet Pods | auto |
statefulset.podAntiAffinity.topologyKey |
The topologyKey for auto anti-affinity rules | kubernetes.io/hostname |
statefulset.podAntiAffinity.type |
Type of auto anti-affinity rules | soft |
statefulset.podAntiAffinity.weight |
Weight for soft auto anti-affinity rules |
100 |
statefulset.nodeSelector |
Node labels for StatefulSet Pods assignment | {} |
statefulset.priorityClassName |
PriorityClassName for StatefulSet Pods | "" |
statefulset.tolerations |
Node taints to tolerate by StatefulSet Pods | [] |
statefulset.topologySpreadConstraints |
Topology Spread Constraints rules of StatefulSet Pods | auto |
statefulset.topologySpreadConstraints.maxSkew |
Degree to which Pods may be unevenly distributed | 1 |
statefulset.topologySpreadConstraints.topologyKey |
The key of node labels | topology.kubernetes.io/zone |
statefulset.topologySpreadConstraints.whenUnsatisfiable |
ScheduleAnyway/DoNotSchedule for unsatisfiable constraints |
ScheduleAnyway |
statefulset.resources |
Resource requests and limits for StatefulSet Pods | {} |
statefulset.customLivenessProbe |
Custom Liveness probe | {} |
statefulset.customReadinessProbe |
Custom Rediness probe | {} |
service.ports.grpc.external.port |
CockroachDB primary serving port in Services | 26257 |
service.ports.grpc.external.name |
CockroachDB primary serving port name in Services | grpc |
service.ports.grpc.internal.port |
CockroachDB inter-communication port in Services | 26257 |
service.ports.grpc.internal.name |
CockroachDB inter-communication port name in Services | grpc-internal |
service.ports.http.port |
CockroachDB HTTP port in Services | 8080 |
service.ports.http.name |
CockroachDB HTTP port name in Services | http |
service.public.type |
Public Service type | ClusterIP |
service.public.labels |
Additional labels of public Service | {"app.kubernetes.io/component": "cockroachdb"} |
service.public.annotations |
Additional annotations of public Service | {} |
service.discovery.labels |
Additional labels of discovery Service | {"app.kubernetes.io/component": "cockroachdb"} |
service.discovery.annotations |
Additional annotations of discovery Service | {} |
ingress.enabled |
Enable ingress resource for CockroachDB | false |
ingress.labels |
Additional labels of Ingress | {} |
ingress.annotations |
Additional annotations of Ingress | {} |
ingress.paths |
Paths for the default host | [/] |
ingress.hosts |
CockroachDB Ingress hostnames | [] |
ingress.tls[0].hosts |
CockroachDB Ingress tls hostnames | nil |
ingress.tls[0].secretName |
CockroachDB Ingress tls secret name | nil |
prometheus.enabled |
Enable automatic monitoring of all instances when Prometheus is running | true |
serviceMonitor.enabled |
Create ServiceMonitor Resource for scraping metrics using PrometheusOperator | false |
serviceMonitor.labels |
Additional labels of ServiceMonitor | {} |
serviceMonitor.annotations |
Additional annotations of ServiceMonitor | {} |
serviceMonitor.interval |
ServiceMonitor scrape metrics interval | 10s |
serviceMonitor.scrapeTimeout |
ServiceMonitor scrape timeout | nil |
serviceMonitor.namespaced |
Limit ServiceMonitor to current namespace | false |
storage.hostPath |
Absolute path on host to store data | "" |
storage.persistentVolume.enabled |
Whether to use PersistentVolume to store data | yes |
storage.persistentVolume.size |
PersistentVolume size | 100Gi |
storage.persistentVolume.storageClass |
PersistentVolume class | "" |
storage.persistentVolume.labels |
Additional labels of PersistentVolumeClaim | {} |
storage.persistentVolume.annotations |
Additional annotations of PersistentVolumeClaim | {} |
init.labels |
Additional labels of init Job and its Pod | {"app.kubernetes.io/component": "init"} |
init.jobAnnotations |
Additional annotations of the init Job itself | {} |
init.annotations |
Additional annotations of the Pod of init Job | {} |
init.affinity |
Affinity rules of init Job Pod | {} |
init.nodeSelector |
Node labels for init Job Pod assignment | {} |
init.tolerations |
Node taints to tolerate by init Job Pod | [] |
init.resources |
Resource requests and limits for the cluster-init container |
{} |
tls.enabled |
Whether to run securely using TLS certificates | no |
tls.serviceAccount.create |
Whether to create a new RBAC service account | yes |
tls.serviceAccount.name |
Name of RBAC service account to use | "" |
tls.copyCerts.image |
Image used in copy certs init container | busybox |
tls.copyCerts.resources |
Resource requests and limits for the copy-certs container |
{} |
tls.certs.provided |
Bring your own certs scenario, i.e certificates are provided | no |
tls.certs.clientRootSecret |
If certs are provided, secret name for client root cert | cockroachdb-root |
tls.certs.nodeSecret |
If certs are provided, secret name for node cert | cockroachdb-node |
tls.certs.tlsSecret |
Own certs are stored in TLS secret | no |
tls.certs.selfSigner.enabled |
Whether cockroachdb should generate its own self-signed certs | true |
tls.certs.selfSigner.caProvided |
Bring your own CA scenario. This CA will be used to generate node and client cert | false |
tls.certs.selfSigner.caSecret |
If CA is provided, secret name for CA cert | "" |
tls.certs.selfSigner.minimumCertDuration |
Minimum cert duration for all the certs, all certs duration will be validated against this duration | 624h |
tls.certs.selfSigner.caCertDuration |
Duration of CA cert in hour | 43824h |
tls.certs.selfSigner.caCertExpiryWindow |
Expiry window of CA cert means a window before actual expiry in which CA cert should be rotated | 648h |
tls.certs.selfSigner.clientCertDuration |
Duration of client cert in hour | `672h |
tls.certs.selfSigner.clientCertExpiryWindow |
Expiry window of client cert means a window before actual expiry in which client cert should be rotated | 48h |
tls.certs.selfSigner.nodeCertDuration |
Duration of node cert in hour | 8760h |
tls.certs.selfSigner.nodeCertExpiryWindow |
Expiry window of node cert means a window before actual expiry in which node certs should be rotated | 168h |
tls.certs.selfSigner.rotateCerts |
Whether to rotate the certs generate by cockroachdb | true |
tls.certs.selfSigner.readinessWait |
Wait time for each cockroachdb replica to become ready once it comes in running state. Only considered when rotateCerts is set to true | 30s |
tls.certs.selfSigner.podUpdateTimeout |
Wait time for each cockroachdb replica to get to running state. Only considered when rotateCerts is set to true | 2m |
tls.certs.certManager |
Provision certificates with cert-manager | false |
tls.certs.certManagerIssuer.group |
IssuerRef group to use when generating certificates | cert-manager.io |
tls.certs.certManagerIssuer.kind |
IssuerRef kind to use when generating certificates | Issuer |
tls.certs.certManagerIssuer.name |
IssuerRef name to use when generating certificates | cockroachdb |
tls.certs.certManagerIssuer.clientCertDuration |
Duration of client cert in hours | 672h |
tls.certs.certManagerIssuer.clientCertExpiryWindow |
Expiry window of client cert means a window before actual expiry in which client cert should be rotated | 48h |
tls.certs.certManagerIssuer.nodeCertDuration |
Duration of node cert in hours | 8760h |
tls.certs.certManagerIssuer.nodeCertExpiryWindow |
Expiry window of node certificates means a window before actual expiry in which node certs should be rotated. | 168h |
tls.selfSigner.image.repository |
Image to use for self signing TLS certificates | cockroachlabs-helm-charts/cockroach-self-signer-cert |
tls.selfSigner.image.tag |
Image tag to use for self signing TLS certificates | 0.1 |
tls.selfSigner.image.pullPolicy |
Self signing TLS certificates container pull policy | IfNotPresent |
tls.selfSigner.image.credentials |
registry, user and pass credentials to pull private image |
{} |
networkPolicy.enabled |
Enable NetworkPolicy for CockroachDB's Pods | no |
networkPolicy.ingress.grpc |
Whitelist resources to access gRPC port of CockroachDB's Pods | [] |
networkPolicy.ingress.http |
Whitelist resources to access gRPC port of CockroachDB's Pods | [] |
Override the default parameters using the --set key=value[,key=value] argument to helm install.
Alternatively, a YAML file that specifies custom values for the parameters can be provided while installing the chart. For example:
helm install my-release -f my-values.yaml cockroachdb/cockroachdbTip: You can use the default values.yaml
Once you've created the cluster, you can start talking to it by connecting to its -public Service. CockroachDB is PostgreSQL wire protocol compatible, so there's a wide variety of supported clients. As an example, we'll open up a SQL shell using CockroachDB's built-in shell and play around with it a bit, like this (likely needing to replace my-release-cockroachdb-public with the name of the -public Service that was created with your installed chart):
kubectl run cockroach-client --rm -it \
--image=cockroachdb/cockroach \
--restart=Never \
-- sql --insecure --host my-release-cockroachdb-publicWaiting for pod default/cockroach-client to be running, status is Pending,
pod ready: false
If you don't see a command prompt, try pressing enter.
root@my-release-cockroachdb-public:26257> SHOW DATABASES;
+--------------------+
| Database |
+--------------------+
| information_schema |
| pg_catalog |
| system |
+--------------------+
(3 rows)
root@my-release-cockroachdb-public:26257> CREATE DATABASE bank;
CREATE DATABASE
root@my-release-cockroachdb-public:26257> CREATE TABLE bank.accounts (id INT
PRIMARY KEY, balance DECIMAL);
CREATE TABLE
root@my-release-cockroachdb-public:26257> INSERT INTO bank.accounts VALUES
(1234, 10000.50);
INSERT 1
root@my-release-cockroachdb-public:26257> SELECT * FROM bank.accounts;
+------+---------+
| id | balance |
+------+---------+
| 1234 | 10000.5 |
+------+---------+
(1 row)
root@my-release-cockroachdb-public:26257> \q
Waiting for pod default/cockroach-client to terminate, status is Running
pod "cockroach-client" deleted
If you are running in secure mode, you will have to provide a client certificate to the cluster in order to authenticate, so the above command will not work. See here for an example of how to set up an interactive SQL shell against a secure cluster or here for an example application connecting to a secure cluster.
Because our pod spec includes regular health checks of the CockroachDB processes, simply running kubectl get pods and looking at the STATUS column is sufficient to determine the health of each instance in the cluster.
If you want more detailed information about the cluster, the best place to look is the Admin UI.
If you want to see information about how the cluster is doing, you can try pulling up the CockroachDB Admin UI by port-forwarding from your local machine to one of the pods (replacing my-release-cockroachdb-0 with the name of one of your pods:
kubectl port-forward my-release-cockroachdb-0 8080You should then be able to access the Admin UI by visiting http://localhost:8080/ in your web browser.
If any CockroachDB member fails, it is restarted or recreated automatically by the Kubernetes infrastructure, and will re-join the cluster automatically when it comes back up. You can test this scenario by killing any of the CockroachDB pods:
kubectl delete pod my-release-cockroachdb-1kubectl get pods -l "app.kubernetes.io/instance=my-release,app.kubernetes.io/component=cockroachdb"NAME READY STATUS RESTARTS AGE
my-release-cockroachdb-0 1/1 Running 0 5m
my-release-cockroachdb-2 1/1 Running 0 5m
After a while:
kubectl get pods -l "app.kubernetes.io/instance=my-release,app.kubernetes.io/component=cockroachdb"NAME READY STATUS RESTARTS AGE
my-release-cockroachdb-0 1/1 Running 0 5m
my-release-cockroachdb-1 1/1 Running 0 20s
my-release-cockroachdb-2 1/1 Running 0 5m
You can check the state of re-joining from the new pod's logs:
kubectl logs my-release-cockroachdb-1[...]
I161028 19:32:09.754026 1 server/node.go:586 [n1] node connected via gossip and
verified as part of cluster {"35ecbc27-3f67-4e7d-9b8f-27c31aae17d6"}
[...]
cockroachdb-0.my-release-cockroachdb.default.svc.cluster.local:26257
build: beta-20161027-55-gd2d3c7f @ 2016/10/28 19:27:25 (go1.7.3)
admin: http://0.0.0.0:8080
sql:
postgresql://root@my-release-cockroachdb-1.my-release-cockroachdb.default.svc.cluster.local:26257?sslmode=disable
logs: cockroach-data/logs
store[0]: path=cockroach-data
status: restarted pre-existing node
clusterID: {35ecbc27-3f67-4e7d-9b8f-27c31aae17d6}
nodeID: 2
[...]
To enable NetworkPolicy for CockroachDB, install a networking plugin that implements the Kubernetes NetworkPolicy spec, and set networkPolicy.enabled to yes/true.
For Kubernetes v1.5 & v1.6, you must also turn on NetworkPolicy by setting the DefaultDeny Namespace annotation. Note: this will enforce policy for all pods in the Namespace:
kubectl annotate namespace default "net.beta.kubernetes.io/network-policy={\"ingress\":{\"isolation\":\"DefaultDeny\"}}"For more precise policy, set networkPolicy.ingress.grpc and networkPolicy.ingress.http rules. This will only allow pods that match the provided rules to connect to CockroachDB.
Scaling should be managed via the helm upgrade command. After resizing your cluster on your cloud environment (e.g., GKE or EKS), run the following command to add a pod. This assumes you scaled from 3 to 4 nodes:
helm upgrade \
my-release \
cockroachdb/cockroachdb \
--set statefulset.replicas=4 \
--reuse-valuesNote, that if you are running in secure mode (tls.enabled is yes/true) and increase the size of your cluster, you will also have to approve the CSR (certificate-signing request) of each new node (using kubectl get csr and kubectl certificate approve).