Skip to content

v0.78.0

Choose a tag to compare

@cooloo9871 cooloo9871 released this 17 Nov 01:32
· 9 commits to main since this release

CRI-O nodes work with Tetragon's default settings

On CRI-O, Tetragon names no pod for the processes of a container, so Behavior Discovery learned nothing and Security Events had no namespace or pod. Sentinel now works out the pod itself, from the container runtime that started each process. Processes that were already running are covered too. Nothing changes on containerd.

Upgrading from v0.77.0 on CRI-O: switch two Tetragon settings back

v0.77.0's installers switched on tetragon.cri.enabled and tetragon.cgidmap.enabled for CRI-O nodes. With those on, a Tracing Policy that names a namespace or a pod selector blocks nothing. This release no longer sets them. If your cluster has them on, switch them off:

helm repo update cilium
helm -n kube-system upgrade tetragon cilium/tetragon --version <installed version> --reuse-values \
  --set tetragon.cri.enabled=false \
  --set tetragon.cgidmap.enabled=false
kubectl -n kube-system rollout status ds/tetragon
kubectl -n sentinel-system rollout restart deploy/sentinel

helm -n kube-system list shows the installed version. For an offline install, apply manifests/tetragon.yaml from this bundle. Details: docs/install.md.

Images

# K8s Sentinel v0.78.0: every image an offline install needs.
# Tetragon chart 1.8.0, Trivy Operator chart 0.38.1.
ghcr.io/cooloo9871/sentinel:v0.78.0
mirror.gcr.io/aquasec/trivy:0.76.1
mirror.gcr.io/aquasec/trivy-operator:0.36.1
quay.io/cilium/hubble-export-stdout:v1.1.1
quay.io/cilium/tetragon-operator:v1.8.0
quay.io/cilium/tetragon:v1.8.0
# artifacts
# Trivy's vulnerability databases. They are OCI artifacts, not container
# images: docker pull cannot fetch them; skopeo and oras can. They change
# daily, and a scan is as current as the copy in your registry.
mirror.gcr.io/aquasec/trivy-db:2
mirror.gcr.io/aquasec/trivy-java-db:1