You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/current/v25.2/configure-cockroachdb-kubernetes-operator.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ docs_area: deploy
9
9
10
10
This page explains how to configure Kubernetes cluster resources such as memory, CPU, and storage.
11
11
12
-
On a production cluster, the resources you allocate to CockroachDB should be proportionate to your machine types and workload. We recommend that you determine and set these values before deploying the cluster, but you can also update the values on a running cluster.
12
+
On a production cluster, the resources you allocate to CockroachDB should be proportionate to your machine types and workload. Cockroach Labs recommends that you determine and set these values before deploying the cluster, but you can also update the values on a running cluster.
13
13
14
14
{{site.data.alerts.callout_info}}
15
15
Run `kubectl describe nodes` to see the available resources on the instances that you have provisioned.
@@ -20,12 +20,12 @@ Run `kubectl describe nodes` to see the available resources on the instances tha
20
20
You can set the CPU and memory resources allocated to the CockroachDB container on each pod.
21
21
22
22
{{site.data.alerts.callout_info}}
23
-
1 CPU in Kubernetes is equivalent to 1 vCPU or 1 hyperthread. For best practices on provisioning CPU and memory for CockroachDB, see the [Production Checklist](recommended-production-settings.html#hardware).
23
+
1 CPU in Kubernetes is equivalent to 1 vCPU or 1 hyperthread. For best practices on provisioning CPU and memory for CockroachDB, refer to the [Production Checklist](recommended-production-settings.html#hardware).
24
24
{{site.data.alerts.end}}
25
25
26
26
Specify CPU and memory values in `cockroachdb.crdbCluster.resources.limits` and `cockroachdb.crdbCluster.resources.requests` in the values file used to [deploy the cluster](deploy-cockroachdb-with-kubernetes-operator.html#initialize-the-cluster):
27
27
28
-
```yaml
28
+
~~~yaml
29
29
cockroachdb:
30
30
crdbCluster:
31
31
resources:
@@ -35,7 +35,7 @@ cockroachdb:
35
35
requests:
36
36
cpu: 4000m
37
37
memory: 16Gi
38
-
```
38
+
~~~
39
39
40
40
Apply the new settings to the cluster:
41
41
@@ -55,7 +55,7 @@ For more information on how Kubernetes handles resources, see the [Kubernetes do
55
55
56
56
Each CockroachDB node reserves a portion of its available memory for its cache and for storing temporary data for SQL queries. For more information on these settings, see the [Production Checklist](recommended-production-settings.html#cache-and-sql-memory-size).
57
57
58
-
The Kubernetes operator dynamically sets cache size and SQL memory size each to 25% (the recommended percent) of the available memory, which depends on the memory request and limit you [specified](#memory-and-cpu) for your configuration. These values can be modified by adding the `cache` or `max-sql-memory` fields to `cockroachdb.crdbCluster.flags`, which is equivalent to appending `--cache` or `--max-sql-memory` as [cockroach start flags](cockroach-start.html#flags).
58
+
The Kubernetes operator dynamically sets cache size and SQL memory size each to 25% (the recommended percentage) of the available memory, which depends on the memory request and limit you [specified](#memory-and-cpu) for your configuration. These values can be modified by adding the `cache` or `max-sql-memory` fields to `cockroachdb.crdbCluster.flags`, which is equivalent to appending `--cache` or `--max-sql-memory` as [cockroach start flags](cockroach-start.html#flags).
59
59
60
60
## Persistent storage
61
61
@@ -109,7 +109,7 @@ The Operator separates network traffic into three ports:
0 commit comments