Kubernetes Configuration

Add Tolerations, Affinity, and Node Selectors

Tolerations, Affinity, and Node Selectors for the Sensor pods may be specified via Helm values. For example:

sensor:
  tolerations:
    - key: node-role.kubernetes.io/control-plane
      operator: Exists
      effect: NoSchedule
    - key: "devops"
      operator: "Equal"
      value: "dedicated"
      effect: "NoSchedule"
  nodeSelector:
    kubernetes.io/hostname: "mavros"
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchExpressions:
          - key: topology.kubernetes.io/zone
            operator: In
            values:
            - antarctica-east1
            - antarctica-west1
      preferredDuringSchedulingIgnoredDuringExecution:
      - weight: 1
        preference:
          matchExpressions:
          - key: another-node-label-key
            operator: In
            values:
            - another-node-label-value

---

Installing the Sensor

Installing a Sensor for the first time, or adding one on another host? Start at Install eBPF Sensor, or go straight to your platform:

Platform	Guide
Kubernetes	Sensor on Kubernetes
AWS ECS	Sensor on AWS ECS using Terraform
Docker	Sensor via Docker
Debian / Ubuntu	Sensor via APT Package
RHEL / Amazon Linux	Sensor via YUM Package
Linux host (systemd)	Sensor as a Systemd Service

Related configuration guides

• Manage Sensor Configuration — the full configuration file and every setting
• API Traffic Capture Filters — control exactly which traffic is captured
• Setting up TLS from Sensor to Satellite — encrypt the connection to the Satellite