Skip to main content

Deploy with Kubernetes (Helm)

For production at scale (multiple nodes, high availability, autoscaling), CentralOps ships a Helm chart that provisions the API, the frontend, the collection workers (Celery), the scheduler, plus HPA (autoscaling), PDB (availability during maintenance), and NetworkPolicies. It is the same Docker artifact as Docker Compose — only the orchestration changes.

When to use

Choose Kubernetes when you need horizontal scaling, multi-node resilience, or integration with an existing cluster. For a single server, Docker Compose is simpler.

Prerequisites​

  • A Kubernetes 1.27+ cluster with kubectl access.
  • Helm 3.9+.
  • A Postgres and a Redis — managed (recommended) or inside the cluster.

Step by step​

1. Prepare the values​

Create a values.override.yaml with the minimum for your environment:

image:
  repository: ghcr.io/segark-oficial/centralops
  tag: "v1.0.0"          # fixe uma tag imutável em produção

frontendImage:
  repository: ghcr.io/segark-oficial/centralops-frontend
  tag: "v1.0.0"

# Segredos essenciais (use um Secret existente em produção)
config:
  appEnv: production
  # APP_MASTER_KEY e a URL do banco devem vir de um Secret — ver "Segredos" abaixo.

postgres:
  # aponte para o seu Postgres gerido
  host: postgres.exemplo.internal
  database: centralops

autoscaling:
  enabled: true
  minReplicas: 2
  maxReplicas: 6

2. Install​

kubectl create namespace centralops
helm install centralops kubernetes/helm/centralops \
  --namespace centralops \
  -f values.override.yaml

3. Verify​

kubectl -n centralops rollout status deploy/centralops-api
kubectl -n centralops get pods
kubectl -n centralops port-forward svc/centralops-api 8080:80 &
curl -fsS http://localhost:8080/readyz

Essential secrets​

Never put secrets in values.yaml. Create a Secret and reference it:

kubectl -n centralops create secret generic centralops-secrets \
  --from-literal=APP_MASTER_KEY="<chave-de-32+-caracteres>" \
  --from-literal=DATABASE_URL="postgresql+psycopg2://user:senha@host:5432/centralops"
KeyWhat it is for
APP_MASTER_KEYMaster encryption key for integration secrets (≥ 32 chars).
DATABASE_URLConnection to the production Postgres.
POSTGRES_PASSWORDIf you use the chart's in-cluster Postgres.

The complete variable reference is in Configuration.

What the chart delivers​

  • API + frontend + Celery workers + beat as separate Deployments (release decoupled from the UI).
  • HPA to scale the API/workers by CPU.
  • PodDisruptionBudget so maintenance does not take down all replicas at once.
  • NetworkPolicies restricting traffic between components.
  • License keyring (ConfigMap with public keys) to verify the Enterprise license offline — see Editions & Upgrade.

Next steps​