Skip to content

Feedback: Deploy CockroachDB with the CockroachDB Operator #23078

@nnaka2992

Description

@nnaka2992

Page: https://cockroachlabs.com/docs/v26.1/deploy-cockroachdb-with-cockroachdb-operator.html

What is the reason for your feedback?

[ ] Missing the information I need

[ ] Too complicated

[ ] Out of date

[x] Something is broken

[ ] Other

Additional details

Issues encountered following the "Deploy CockroachDB with the CockroachDB Operator" guide on a GKE regional cluster (v1.34, e2-standard-4 x 3 zones):

  1. Incorrect resource configuration path (Values documentation)
    The documentation references cockroachdb.crdbCluster.podTemplate.spec.resources for setting CPU/memory, but the correct path in the CRD schema is cockroachdb.crdbCluster.podTemplate.spec.containers[].resources. Using the documented path causes: spec.template.spec.podTemplate.spec.resources: field not declared in schema.

  2. Missing -n in client-secure pod commands
    The document does not specify the namespace flag when running:

    • kubectl create -f client-secure.yaml
    • kubectl exec -it cockroachdb-client-secure -- ...

    Without -n , the pod is created in the default namespace where the cockroachdb ServiceAccount doesn't exist, resulting in: error looking up service account default/cockroachdb: serviceaccount "cockroachdb" not found.

Jira issue: DOC-16325

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions