Agent skill

Debugging Cockroachdb Operator Migrations

by cockroachdb in cockroachdb/helm-charts

Debugs CockroachDB Operator migration scenarios, including Helm StatefulSet to v1beta1 CrdbNode migration and public operator v1alpha1 to v1beta1 migration.

Apache-2.0Auto-check passedDevOps & Cloud

Install Debugging Cockroachdb Operator Migrations

skills CLI
$ npx skills add cockroachdb/helm-charts --skill debugging-cockroachdb-operator-migrations -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cockroachdb/helm-charts debugging-cockroachdb-operator-migrations --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cockroachdb/helm-charts.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cockroachdb-onboarding-and-migrations/debugging-cockroachdb-operator-migrations .claude/skills/debugging-cockroachdb-operator-migrations && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
debugging-cockroachdb-operator-migrations
GitHub stars
105
Token cost
~3.6k tokens
SKILL.md length
946 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
Apache-2.0

At a glance

Debugs CockroachDB Operator migration scenarios, including Helm StatefulSet to v1beta1 CrdbNode migration and public operator v1alpha1 to v1beta1 migration.

  • Works in 6 steps: Confirm Migration Documentation and… → Inspect Migration State → Inspect Source Workload → …
  • Migration labels
  • SKILL.md covers When to Use This Skill, Safety Considerations, Execution Discipline and Required Inputs, plus 8 more sections
  • Calls kubectl, jq and helm

What it does

Debugging Cockroachdb Operator Migrations is an agent skill from cockroachdb/helm-charts. Debugs CockroachDB Operator migration scenarios, including Helm StatefulSet to v1beta1 CrdbNode migration and public operator v1alpha1 to v1beta1 migration. Use when migration labels, migration phases, source StatefulSet ownership, converted CRDs, PVC ownership, or post-migration reconciliation are unclear or stuck.

Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: CockroachDB Helm v2 charts and CockroachDB Operator resources, including crdb.cockroachlabs.com/v1alpha1 and v1beta1. Requires read access to the CockroachDB…

It sits in DevOps & Cloud, covering Container orchestration, Accounting and bookkeeping and Debugging. The repository describes itself as: Helm charts for cockroachdb. The licence is Apache-2.0.

When your agent uses it

  • Migration labels
  • Migration phases
  • Source StatefulSet ownership
  • Post-migration reconciliation are unclear

Example prompts

  • “Use the debugging-cockroachdb-operator-migrations skill to debug CockroachDB Operator migration scenarios, including Helm StatefulSet to v1beta1…”
  • “/debugging-cockroachdb-operator-migrations”

Requirements

  • Compatibility (from SKILL.md): CockroachDB Helm v2 charts and CockroachDB Operator resources, including crdb.cockroachlabs.com/v1alpha1 and v1beta1. Requires read access to the CockroachDB namespace and operator namespace; final source StatefulSet deletion must be explicitly approved by the customer.

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Confirm Migration Documentation and Versions
  2. Inspect Migration State
  3. Inspect Source Workload
  4. Interpret Migration Phases
  5. Debug Common Migration Stalls
  6. Post-Migration Operator Stall

What it can do on your machine

Read from SKILL.md and the folder at commit 26e44ff. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • kubectl
    • jq
    • helm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use kubectl and helm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    CockroachDB Helm v2 charts and CockroachDB Operator resources, including crdb.cockroachlabs.com/v1alpha1 and v1beta1. Requires read access to the CockroachDB namespace and operator namespace; final source StatefulSet deletion must be explicitly approved by the customer.

    From compatibility in the SKILL.md frontmatter.

Context cost

Debugging Cockroachdb Operator Migrations loads about 3.6k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 946 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~90
When it runs · the whole SKILL.md, loaded when a task matches
~3.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cockroachdb/helm-charts at commit 26e44ff, republished under its Apache-2.0 licence (© cockroachdb). 946 words, ~3,626 tokens.

Download SKILL.mdSave it as .claude/skills/debugging-cockroachdb-operator-migrations/SKILL.md (or your agent's skills folder).
name
debugging-cockroachdb-operator-migrations
description
Debugs CockroachDB Operator migration scenarios, including Helm StatefulSet to v1beta1 CrdbNode migration and public operator v1alpha1 to v1beta1 migration. Use when migration labels, migration phases, source StatefulSet ownership, converted CRDs, PVC ownership, or post-migration reconciliation are unclear or stuck.
compatibility
CockroachDB Helm v2 charts and CockroachDB Operator resources, including crdb.cockroachlabs.com/v1alpha1 and v1beta1. Requires read access to the CockroachDB namespace and operator namespace; final source StatefulSet deletion must be explicitly approved by the customer.
metadata.author
cockroachdb
metadata.version
1.0

Debugging CockroachDB Operator Migrations

Debugs migration from Helm StatefulSet or public operator v1alpha1 workloads to CockroachDB Operator v1beta1 CrdbNode management. Use this after collecting the general baseline from diagnosing-cockroachdb-helm-deployments.

When to Use This Skill

  • A Helm StatefulSet to operator migration is stuck or unclear
  • A public operator v1alpha1 to v1beta1 migration has conversion or webhook issues
  • Migration labels remain start or finalized
  • The schema-grounded migration status field or migration labels report an error
  • Source StatefulSet ownership, pod ownerReferences, or PVC ownerReferences are unclear
  • The operator stops reconciling after migration

Safety Considerations

  • Do not delete the source StatefulSet until the migration phase is finalized and the customer is ready to complete migration.
  • Do not modify the source StatefulSet spec during migration.
  • Do not remove the migration label crdb.io/migrate during an active migration.
  • Do not manually create CrdbNode resources during migration.
  • Do not delete migrated PVCs. They contain CockroachDB data.
  • If the operator stalls after migration, collect the escalation packet before restarting it.

Execution Discipline

  • Execute one step at a time and inspect the output before moving on. Migration phase, source workload state, and ownership determine which later checks are safe.
  • Run every step in the same shell session. The commands rely on OPERATOR_NAMESPACE, CRDB_NAMESPACE, CRDB_MIGRATION_DIR, and the CRDB_*_PATH exports set in Step 1; a fresh shell loses those variables and later jq/kubectl calls will silently target the wrong object.
  • Never infer a target CrdbCluster object name from a Helm release, service name, or CockroachDB image/version string. List CrdbCluster objects and use the exact metadata.name.
  • Before reading migration, condition, or status fields from a CrdbCluster, save the live CRD YAML and derive field paths from the served CRD schema for the object's apiVersion.
  • Do not delete the source StatefulSet, patch labels, patch mode, restart the operator, run Helm upgrades, or change ownerReferences unless the user explicitly approves the action for the target cluster.
  • Do not run interactive kubectl exec shells or debug containers unless the user approves them and the customer policy allows the image/source.
  • In production or when the migration phase is ambiguous, involve TSE or the operator team before changing source or target resources.

Required Inputs

  • Migration type: Helm StatefulSet to operator, or public operator v1alpha1 to v1beta1
  • Source resource name and namespace
  • Target namespace and discovered CrdbCluster.metadata.name
  • Operator namespace and version
  • Values file or migration command used
  • Current migration label and phase
  • Whether the source StatefulSet has already been deleted

Step 1: Confirm Migration Documentation and Versions

bash
export OPERATOR_NAMESPACE="<operator-namespace>"
export CRDB_NAMESPACE="<cockroachdb-namespace>"
export CRDB_HELM_RELEASE="<cockroachdb-release>"
export CRDB_MIGRATION_DIR="${CRDB_MIGRATION_DIR:-$(mktemp -d)}"

kubectl -n "$OPERATOR_NAMESPACE" get deploy cockroach-operator -o jsonpath='{.spec.template.spec.containers[0].image}{"\n"}'
kubectl get crd crdbclusters.crdb.cockroachlabs.com -o jsonpath='{.spec.versions[*].name}{"\n"}'
kubectl get crd crdbclusters.crdb.cockroachlabs.com -o yaml > "$CRDB_MIGRATION_DIR/crdbclusters-crd.yaml"
kubectl get crd crdbclusters.crdb.cockroachlabs.com -o json > "$CRDB_MIGRATION_DIR/crdbclusters-crd.json"
helm -n "$CRDB_NAMESPACE" history "$CRDB_HELM_RELEASE" || true

kubectl -n "$CRDB_NAMESPACE" get crdbcluster -o json | jq -r '
  .items[]
  | [.metadata.name, .apiVersion, (.metadata.labels["app.kubernetes.io/instance"] // ""), (.metadata.labels["crdb.io/migrate"] // ""), (.metadata.labels["crdb.cockroachlabs.com/migration"] // "")]
  | @tsv
'

If no CrdbCluster rows are returned, stop the object-specific migration debugging and report that no live CrdbCluster exists in the namespace. You may collect CrdbNode owner references and labels as teardown evidence, but do not treat those values as a replacement for a discovered CrdbCluster.

If multiple rows are returned, choose the target by metadata.name; do not use a CockroachDB version or image tag as the object name.

bash
export CRDBCLUSTER="<metadata.name-from-crdbcluster-list>"
test -n "$CRDBCLUSTER"

kubectl -n "$CRDB_NAMESPACE" get crdbcluster "$CRDBCLUSTER" -o yaml > "$CRDB_MIGRATION_DIR/crdbcluster.yaml"
kubectl -n "$CRDB_NAMESPACE" get crdbcluster "$CRDBCLUSTER" -o json > "$CRDB_MIGRATION_DIR/crdbcluster.json"

export CRDBCLUSTER_API_VERSION="$(jq -r '.apiVersion | split("/")[-1]' "$CRDB_MIGRATION_DIR/crdbcluster.json")"
export CRDBCLUSTER_SCHEMA_JSON="$CRDB_MIGRATION_DIR/crdbcluster-schema.json"
jq -e --arg version "$CRDBCLUSTER_API_VERSION" '
  .spec.versions[] | select(.name == $version) | .schema.openAPIV3Schema
' "$CRDB_MIGRATION_DIR/crdbclusters-crd.json" > "$CRDBCLUSTER_SCHEMA_JSON"

crdb_schema_has() {
  jq -e --arg path "$1" '
    def has_schema_path($schema; $parts):
      if ($parts | length) == 0 then true
      elif (($schema.properties? // {}) | has($parts[0])) then
        has_schema_path($schema.properties[$parts[0]]; $parts[1:])
      else false
      end;
    has_schema_path(.; $path | split("."))
  ' "$CRDBCLUSTER_SCHEMA_JSON" >/dev/null
}

crdb_first_schema_path() {
  for schema_path in "$@"; do
    if crdb_schema_has "$schema_path"; then
      printf '%s\n' "$schema_path"
      return 0
    fi
  done
  printf '\n'
}

export CRDB_MODE_PATH="$(crdb_first_schema_path spec.mode)"
export CRDB_MIGRATION_PATH="$(crdb_first_schema_path status.migration)"
export CRDB_CONDITIONS_PATH="$(crdb_first_schema_path status.conditions)"
export CRDB_OBSERVED_GENERATION_PATH="$(crdb_first_schema_path status.observedGeneration)"

printf '%s\n' \
  "apiVersion=$CRDBCLUSTER_API_VERSION" \
  "mode=$CRDB_MODE_PATH" \
  "migration=$CRDB_MIGRATION_PATH" \
  "conditions=$CRDB_CONDITIONS_PATH" \
  "observedGeneration=$CRDB_OBSERVED_GENERATION_PATH"

Check the local migration guide and chart changelog for version-specific migration fixes:

Step 2: Inspect Migration State

bash
jq \
  --arg modePath "$CRDB_MODE_PATH" \
  --arg migrationPath "$CRDB_MIGRATION_PATH" \
  --arg conditionsPath "$CRDB_CONDITIONS_PATH" \
  --arg observedGenerationPath "$CRDB_OBSERVED_GENERATION_PATH" \
  '
  def value($path): if $path == "" then null else getpath($path | split(".")) end;
  {
  apiVersion,
  name: .metadata.name,
  schemaPaths: {
    mode: $modePath,
    migration: $migrationPath,
    conditions: $conditionsPath,
    observedGeneration: $observedGenerationPath
  },
  mode: value($modePath),
  migrateLabel: .metadata.labels["crdb.io/migrate"],
  migrationStatus: .metadata.labels["crdb.cockroachlabs.com/migration"],
  migration: value($migrationPath),
  conditions: value($conditionsPath),
  generation: .metadata.generation,
  observedGeneration: value($observedGenerationPath)
}' "$CRDB_MIGRATION_DIR/crdbcluster.json"

kubectl -n "$OPERATOR_NAMESPACE" logs -l app=cockroach-operator --tail=300 | grep -Ei 'migrationctrl|migration|phase|cert' || true
kubectl -n "$CRDB_NAMESPACE" get crdbnodes -o wide
kubectl -n "$CRDB_NAMESPACE" get crdbnodes -o yaml

Step 3: Inspect Source Workload

For Helm StatefulSet migration:

bash
kubectl -n "$CRDB_NAMESPACE" get sts <source-statefulset> -o json | jq '{
  replicas: .spec.replicas,
  readyReplicas: .status.readyReplicas,
  migrateLabel: .metadata.labels["crdb.io/migrate"],
  ownerReferences: .metadata.ownerReferences
}'

kubectl -n "$CRDB_NAMESPACE" get sts <source-statefulset> -o yaml
kubectl -n "$CRDB_NAMESPACE" get pods -l app.kubernetes.io/name=cockroachdb -o yaml | grep -E 'name:|ownerReferences:|kind:|uid:|controller:' -A8
kubectl -n "$CRDB_NAMESPACE" get pvc -o yaml | grep -E 'name:|ownerReferences:|kind:|uid:|controller:' -A8

For public operator v1alpha1 migration:

bash
kubectl -n "$CRDB_NAMESPACE" get crdbcluster.crdb.cockroachlabs.com "$CRDBCLUSTER" -o yaml
kubectl -n "$CRDB_NAMESPACE" get crdbcluster.v1beta1.crdb.cockroachlabs.com "$CRDBCLUSTER" -o yaml 2>&1 || true
kubectl -n "$OPERATOR_NAMESPACE" get svc cockroach-webhook-service
kubectl -n "$OPERATOR_NAMESPACE" get endpoints cockroach-webhook-service
kubectl get validatingwebhookconfigurations | grep cockroach

The operator supports both v1alpha1 and v1beta1 through conversion webhooks. If conversion fails, check webhook service health and operator logs.

Show full SKILL.md (410 more words)Show less

Step 4: Interpret Migration Phases

PhaseWhat HappensWhat to Check
InitOperator validates prerequisites and prepares migrationMigration label is start; check operator logs for validation errors
CertMigrationOperator migrates or creates TLS certificate resourcesCheck certificate Secrets, CA resources, cert-manager resources, and cert metadata
PodMigrationOperator creates CrdbNode resources to take over pods from the StatefulSetCheck CrdbNode creation and pod ownerReferences
FinalizationOperator sets mode=MutableOnly and stops source migration workCrdbCluster mode should be MutableOnly; migration label should be finalized
CompleteCustomer deletes the source StatefulSet and the delete event triggers final reconcileStatefulSet must be manually deleted only after finalization; migration label should become complete

Step 5: Debug Common Migration Stalls

Migration Not Progressing
bash
jq --arg migrationPath "$CRDB_MIGRATION_PATH" '
  def value($path): if $path == "" then null else getpath($path | split(".")) end;
  {migrationPath: $migrationPath, migration: value($migrationPath)}
' "$CRDB_MIGRATION_DIR/crdbcluster.json"
kubectl -n "$OPERATOR_NAMESPACE" logs -l app=cockroach-operator --tail=300 | grep -Ei 'migration|phase|cert|error' || true
kubectl -n "$OPERATOR_NAMESPACE" get deploy cockroach-operator -o jsonpath='{.spec.template.spec.containers[0].args}{"\n"}'

Check:

  • The migration feature is enabled in operator args, if the deployed version uses a feature flag.
  • The source StatefulSet still exists when phase is before finalized.
  • The source StatefulSet spec has not been changed mid-migration.
  • Certificate prerequisites are present and trusted.
  • CrdbNode objects are being created and observed.
CertMigration Issues

Use configuring-cockroachdb-helm-tls. Confirm:

  • CA ConfigMap or Secret exists.
  • Node, HTTP, and root client certificate resources exist.
  • Certificate expiry, issuer, subject, and SANs match generated pod DNS names.
  • Cert-manager Certificate resources are Ready, when cert-manager is used.
  • Secret keys are present without printing private key values.
PodMigration Issues
bash
kubectl -n "$CRDB_NAMESPACE" get pods -l app.kubernetes.io/name=cockroachdb -o wide
kubectl -n "$CRDB_NAMESPACE" describe pods -l app.kubernetes.io/name=cockroachdb
kubectl -n "$CRDB_NAMESPACE" get crdbnodes -o 'custom-columns=NAME:.metadata.name,DECOMMISSION:.status.decommission,NODE_ID:.status.nodeID,OBSERVED:.status.observedGeneration'
kubectl -n "$CRDB_NAMESPACE" get pvc -o json | jq '.items[] | {name: .metadata.name, ownerReferences: .metadata.ownerReferences, storageClass: .spec.storageClassName, capacity: .status.capacity}'

Check:

  • CrdbNode resources are created for expected pods.
  • Pods and PVCs have expected ownership after the operator takes over.
  • PVCs are not orphaned before deleting source resources.
Finalization or Completion Stuck

Check:

  • mode is MutableOnly, not Disabled.
  • migration label is finalized before deleting the source StatefulSet.
  • source StatefulSet deletion happened only after finalization.
  • migration label eventually becomes complete.
  • operator logs show a final reconcile after the source StatefulSet delete event.

Step 6: Post-Migration Operator Stall

If the operator stops reconciling after migration completes:

  1. Check the initialization condition. If missing on an already-initialized cluster, the operator may try to initialize and block.
  2. Verify mode is MutableOnly.
  3. Verify the migration label is complete, not start or finalized.
  4. Use collecting-cockroachdb-operator-escalation-packet to collect pprof goroutine dump, metrics, and logs before restart.

Output Format

Return findings in this order:

  1. Migration type and current phase
  2. Source workload state
  3. Target CrdbCluster mode, migration labels, and schema-grounded migration status
  4. CrdbNode, pod, and PVC ownership state
  5. Current blocker and likely cause
  6. Safe next action
  7. Whether escalation packet collection is required

References

© cockroachdb, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/cockroachdb-onboarding-and-migrations/debugging-cockroachdb-operator-migrations of cockroachdb/helm-charts.

Open the folder on GitHubat commit 26e44ff

Compare with similar skills

Debugging Cockroachdb Operator Migrations next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Debugging Cockroachdb Operator Migrations compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Debugging Cockroachdb Operator Migrations this skillcockroachdb/helm-charts105—~3.6kAutomated safety check: PassApache-2.0
NGINX Ingress Controller Debuggingnginx/kubernetes-ingress5.1k—~1.7kAutomated safety check: PassApache-2.0
Maintaindevantler-tech/ksail165—~209Automated safety check: PassCustom licence
Operate Cloud Posture Toolchaincyberful/cyberful135—~907Automated safety check: PassAGPL-3.0
Frontend Forge Extension Operationskubesphere/kubesphere17k—~3.2kAutomated safety check: PassCustom licence
Intrinsic Core Debuggingintrinsic-ai/intrinsic-core553—~3.8kAutomated safety check: NotesApache-2.0

Similar skills

  • NGINX Ingress Controller Debugging

    nginx/kubernetes-ingress

    Troubleshooting patterns for the NGINX Ingress Controller: reload failures, custom resources that have no effect, controller panics and snapshot test failures.

    5.1k GitHub stars~1.7k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Maintain

    devantler-tech/ksail

    Repository maintenance for devantler-tech/ksail — triage, bug fixes, CI/workflow health & CI-failure/flaky investigation, docs upkeep, driving every open PR (external contributions included) to a…

    165 GitHub stars~209 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Operate Prowler, Cloudsplaining, cloud CLIs, policy documents, and resource evidence for advanced AWS, Azure, GCP, and Kubernetes-adjacent posture assessment.

    135 GitHub stars~907 tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Runs the lifecycle of FrontendExtension resources in a Kubernetes cluster: create, rebuild, package, publish, unpublish, delete and debug stuck states.

    17k GitHub stars~3.2k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed
  • Intrinsic Core Debugging

    intrinsic-ai/intrinsic-core

    Meta-level debugging workflows, architectural layer isolation, and progressive disclosure routing across Envoy ingress, Kubernetes pods, Behavior Trees, ObjectWorld synchronization, ICON real-time…

    553 GitHub stars~3.8k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Kubernetes Troubleshooting with Inspektor Gadget

    inspektor-gadget/inspektor-gadget

    Traces what the kernel is doing for a misbehaving pod using Inspektor Gadget's eBPF tools, tagged with namespace, pod, container and node, without changing workloads.

    2.9k GitHub stars~2.3k tokensUpdated today
    DevOps & CloudAuto-check passed

More from cockroachdb/helm-charts

  • Collects a complete CockroachDB Operator escalation packet for TSC/TSE or operator-team handoff, including Helm state, Kubernetes resources, logs, operation-specific evidence, pprof goroutine dumps…

    105 GitHub stars~5.1k tokensUpdated 7 days ago
    Auto-check passed
  • Configuring Cockroachdb Helm Tls

    cockroachdb/helm-charts

    Selects and validates TLS settings for CockroachDB Helm chart deployments, including self-signer, cert-manager, and external certificate modes.

    105 GitHub stars~3.8k tokensUpdated 7 days ago
    Auto-check passed
  • Installing Cockroachdb With Helm

    cockroachdb/helm-charts

    Guides customer-facing installation of CockroachDB on Kubernetes using the CockroachDB split Helm charts and operator-managed v1beta1 resources.

    105 GitHub stars~3.4k tokensUpdated 7 days ago
    Auto-check passed
  • Diagnoses failed or unhealthy CockroachDB Helm chart deployments by checking Helm release state, operator health, CrdbCluster and CrdbNode status, pod readiness, RBAC, webhooks, TLS, upgrades…

    105 GitHub stars~6.8k tokensUpdated 7 days ago
    Auto-check passed
  • Validates CockroachDB Helm chart values and Kubernetes prerequisites for operator-managed multi-region deployments.

    105 GitHub stars~2k tokensUpdated 7 days ago
    Auto-check passed

Questions about Debugging Cockroachdb Operator Migrations

What does Debugging Cockroachdb Operator Migrations do?

Debugs CockroachDB Operator migration scenarios, including Helm StatefulSet to v1beta1 CrdbNode migration and public operator v1alpha1 to v1beta1 migration. Debugging Cockroachdb Operator Migrations is an agent skill from cockroachdb/helm-charts. Debugs CockroachDB Operator migration scenarios, including Helm StatefulSet to v1beta1 CrdbNode migration and public operator v1alpha1 to v1beta1 migration.

When should I use Debugging Cockroachdb Operator Migrations?

Debugging Cockroachdb Operator Migrations fits situations like: migration labels; migration phases; source StatefulSet ownership; post-migration reconciliation are unclear.

How do I install Debugging Cockroachdb Operator Migrations in Claude Code?

Run `npx skills add cockroachdb/helm-charts --skill debugging-cockroachdb-operator-migrations -a claude-code`. Or copy the skill folder (skills/cockroachdb-onboarding-and-migrations/debugging-cockroachdb-operator-migrations in cockroachdb/helm-charts) into .claude/skills/debugging-cockroachdb-operator-migrations in your project. Claude Code loads it when a task matches its description.

How do I install Debugging Cockroachdb Operator Migrations in Codex?

Run `npx skills add cockroachdb/helm-charts --skill debugging-cockroachdb-operator-migrations -a codex`. Or copy the skill folder (skills/cockroachdb-onboarding-and-migrations/debugging-cockroachdb-operator-migrations in cockroachdb/helm-charts) into .agents/skills/debugging-cockroachdb-operator-migrations in your project. Codex loads it when a task matches its description.

Can I use Debugging Cockroachdb Operator Migrations in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cockroachdb/helm-charts --skill debugging-cockroachdb-operator-migrations -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debugging-cockroachdb-operator-migrations, .gemini/skills/debugging-cockroachdb-operator-migrations, .github/skills/debugging-cockroachdb-operator-migrations and .opencode/skills/debugging-cockroachdb-operator-migrations in your project.

What does Debugging Cockroachdb Operator Migrations need to run?

Going by SKILL.md and its folder, Debugging Cockroachdb Operator Migrations needs the command-line tools its instructions call (kubectl, jq and helm). Compatibility (from SKILL.md): CockroachDB Helm v2 charts and CockroachDB Operator resources, including crdb.cockroachlabs.com/v1alpha1 and v1beta1. Requires read access to the CockroachDB namespace and operator namespace; final source StatefulSet deletion must be explicitly approved by the customer..

Does Debugging Cockroachdb Operator Migrations access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Debugging Cockroachdb Operator Migrations safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Debugging Cockroachdb Operator Migrations use?

Debugging Cockroachdb Operator Migrations is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Debugging Cockroachdb Operator Migrations use?

About 3.6k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Debugging Cockroachdb Operator Migrations?

Skills that share tags, products or a category with Debugging Cockroachdb Operator Migrations: NGINX Ingress Controller Debugging (nginx/kubernetes-ingress, 5.1k stars), Maintain (devantler-tech/ksail, 165 stars), Operate Cloud Posture Toolchain (cyberful/cyberful, 135 stars) and Frontend Forge Extension Operations (kubesphere/kubesphere, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Debugging Cockroachdb Operator Migrations?

cockroachdb (a GitHub organization) maintains it in cockroachdb/helm-charts, which has 105 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 1, 2026.

Source: cockroachdb/helm-charts on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.