Helm Deployment

Use the Helm chart to install OpsKnight on Kubernetes with repeatable, versioned releases.

Prerequisites

• Kubernetes 1.24+
• Helm 3+
• Access to a container registry
• Ingress controller (recommended for production)

Quick Start

git clone https://github.com/dushyant-rahangdale/opsknight.git
cd opsknight

helm install opsknight ./helm/opsknight \
  --namespace opsknight \
  --create-namespace

Configure Values

Create a values.yaml to override defaults:

image:
  tag: 'latest'

ingress:
  enabled: true
  host: opsknight.example.com

env:
  NEXTAUTH_URL: 'https://opsknight.example.com'
  DATABASE_URL: 'postgresql://user:pass@db:5432/opsknight'

Apply updates with:

helm upgrade --install opsknight ./helm/opsknight \
  --namespace opsknight \
  --create-namespace \
  --values values.yaml

Common Overrides

Resources

resources:
  requests:
    cpu: '200m'
    memory: '512Mi'
  limits:
    cpu: '1'
    memory: '1Gi'

Autoscaling

autoscaling:
  enabled: true
  minReplicas: 2
  maxReplicas: 10
  targetCPUUtilizationPercentage: 70

Ingress TLS

ingress:
  enabled: true
  host: opsknight.example.com
  tls:
    enabled: true
    secretName: opsknight-tls

Secrets Management

Store secrets in your values.yaml or use an external secret manager. Ensure DATABASE_URL, NEXTAUTH_URL, and NEXTAUTH_SECRET are set before first boot.

Next Steps

• Review the Kubernetes guide for scaling, secrets, and ingress setup.
• Add SMTP, notification providers, and integrations via values.yaml.

See Kubernetes Deployment for production hardening.