Deploying Atatus Infra Agent with PostgreSQL Integration in Kubernetes

This guide explains how to deploy the Atatus Infra Agent in a Kubernetes cluster using a values.yaml file instead of entering credentials directly into the manifest. This approach improves security, maintainability, and consistency across environments.

Step 1: Create `values.yaml`

Create a file named values.yaml containing your Atatus and PostgreSQL configuration values.

infra:
  license_key: "YOUR_INFRA_LICENSE_KEY"
  logs_enabled: true
  log_level: "error"

postgres:
  host: "postgres.default.svc.cluster.local"
  username: "atatus"
  password: "atatus-password"

Step 2: Create the Kubernetes Manifests Create a file named atatus-agent.yaml. This manifest reads all actual values from the values.yaml configuration.

apiVersion: v1
kind: ConfigMap
metadata:
  name: atatus-values
data:
  LICENSE_KEY: "${infra.license_key}"
  LOGS_ENABLED: "${infra.logs_enabled}"
  LOG_LEVEL: "${infra.log_level}"

  POSTGRES_HOST: "${postgres.host}"
  POSTGRES_USERNAME: "${postgres.username}"
  POSTGRES_PASSWORD: "${postgres.password}"
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: atatus-main-config
data:
  atatus.yml: |
    license_key: ${LICENSE_KEY}
    logs_enabled: ${LOGS_ENABLED}
    log_level: ${LOG_LEVEL}
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: atatus-postgres-config
data:
  postgresql.yml: |
    metrics:
      - hosts: ["${POSTGRES_HOST}"]
        username: "${POSTGRES_USERNAME}"
        password: "${POSTGRES_PASSWORD}"
        dbm: true
        dbm_postgresql_options:
          collect_database_info:
            enabled: true
            auto_discovery: true
            max_tables: 200
          collect_settings:
            enabled: true
            ignore_patterns:
              - '^pg_toast'
              - '^pg_stat'
              - '^pg_stat_tmp'
              - '^pg_locks'
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: atatus-infra-agent
  labels:
    app: atatus-infra-agent
spec:
  replicas: 1
  selector:
    matchLabels:
      app: atatus-infra-agent
  template:
    metadata:
      labels:
        app: atatus-infra-agent
    spec:
      containers:
        - name: atatus-infra-agent
          image: atatus/atatus-infra-agent:4.3.1
          imagePullPolicy: IfNotPresent
          command: ["/usr/bin/atatus-infra-agent"]
          args: ["-c", "/etc/atatus-infra-agent/"]
          envFrom:
            - configMapRef:
                name: atatus-values
          resources:
            requests:
              cpu: "100m"
              memory: "128Mi"
            limits:
              cpu: "500m"
              memory: "512Mi"
          volumeMounts:
            - name: main-config
              mountPath: /etc/atatus-infra-agent/
            - name: postgres-config
              mountPath: /etc/atatus-infra-agent/conf.d/postgresql.d/
      volumes:
        - name: main-config
          configMap:
            name: atatus-main-config
        - name: postgres-config
          configMap:
            name: atatus-postgres-config

Run on a Specific Node (Optional) If you want the agent to run only on a specific Kubernetes node, add a label. Label the node:

kubectl label node <node-name> atatus-infra-agent=enabled

Add nodeSelector under spec.template.spec:

nodeSelector:
  atatus-infra-agent: "enabled"

Step 3: Load Values and Deploy Create ConfigMap from values.yaml:

kubectl create configmap atatus-values --from-file=values.yaml

Apply the deployment manifest:

kubectl apply -f atatus-agent.yaml

​Step 1: Create values.yaml

Step 1: Create `values.yaml`