provisioning cluster for production

DevOps Community

Skill notes

When to Use This Skill

Creating a new CockroachDB cluster Preparing a development/staging cluster for production go-live Validating hardware and configuration for production readiness Choosing the right deployment tier and sizing For post-deployment health checks: Use reviewing-cluster-health.

Required Context

Question · Options · Why It Matters Deployment tier? · Self-Hosted, Advanced, BYOC, Standard, Basic · Completely different provisioning procedures Environment? · Production, Staging, Development · Determines hardware sizing and configuration rigor

Additional Context (by tier)

If Self-Hosted: Question · Options · Why It Matters Platform? · Bare metal, VMs (AWS/GCP/Azure), Kubernetes · Changes installation and start commands If Kubernetes? · Operator (recommended), Helm, Manual StatefulSet · Determines deployment method Node count? · 3 (minimum), 5, 9+ · Affects topology and replication

Context-Driven Routing

Tier · Go To Self-Hosted · Self-Hosted Provisioning Advanced · Advanced Provisioning BYOC · BYOC Provisioning Standard · Standard Provisioning

Self-Hosted Provisioning

Applies when: Tier = Self-Hosted

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
DevOps
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Required · Vendor-specific
Operating systems
Linux
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Gather Context

Step 1: Gather Context

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.