Skip to main content

Getting Started

Deploy the Saviour Agent Suite to your Kubernetes cluster to start monitoring events, topology, host metrics, and eBPF network flows.

Prerequisites

  • Kubernetes 1.23+
  • kubectl configured for your cluster
  • An ingestion key from the Saviour UISettings → Ingestion Keys

Install

Step 1 — Add your ingestion key as a Secret

kubectl create namespace saviour
kubectl create secret generic saviour-secret \
--from-literal=api-key=YOUR_INGESTION_KEY \
--namespace saviour

Step 2 — Install the chart

helm upgrade --install saviour \
oci://ghcr.io/saviourops-labs/charts/saviour \
--namespace saviour \
--set global.existingSecret=saviour-secret \
--set global.server.url=https://api.saviourops.com \
--set global.cluster.name=my-cluster

Step 3 — Verify agents are running

kubectl get pods -n saviour
# NAME READY STATUS RESTARTS
# saviour-centurion-xxxxx 1/1 Running 0
# saviour-sentinel-xxxxx (node 1) 1/1 Running 0
# saviour-sentinel-xxxxx (node 2) 1/1 Running 0

Step 4 — Confirm in UI

Open app.saviourops.comInfrastructure → your cluster appears within 30 seconds.


Common configuration

ParameterDescriptionExample
global.existingSecretPre-existing Secret name with API keysaviour-secret
global.server.urlSaviour backend URLhttps://api.saviourops.com
global.cluster.nameCluster name shown in the UIprod-east-1
sentinel.ebpf.enabledEnable eBPF (requires kernel 4.18+)true
centurion.enabledDeploy Centuriontrue
sentinel.enabledDeploy Sentineltrue

Production install (PDB + NetworkPolicy + VPA enabled):

helm upgrade --install saviour \
oci://ghcr.io/saviourops-labs/charts/saviour \
-f https://raw.githubusercontent.com/saviourops-labs/saviour/main/agents/helm/saviour/values-production.yaml \
--set global.existingSecret=saviour-secret \
--set global.server.url=https://api.saviourops.com \
--set global.cluster.name=prod-east-1 \
--namespace saviour

Next Steps