Skip to content

Commit

Permalink
[helm] Use http-based liveness probe
Browse files Browse the repository at this point in the history
The previous commit introduced an HTTP endopoint that can be used for
the liveness probe. This patch changes helm to make that default instead
of the tetra status based liveness probe.

The user can still use the tetra status based liveness probe by
defining a values file similar to:
$ cat values.yaml
tetragon:
  livenessProbe: null

Signed-off-by: Anastasios Papagiannis <[email protected]>
  • Loading branch information
tpapagian committed May 27, 2024
1 parent 032ca05 commit d9bd92c
Show file tree
Hide file tree
Showing 3 changed files with 7 additions and 5 deletions.
2 changes: 1 addition & 1 deletion docs/content/en/docs/reference/helm-chart.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion install/kubernetes/tetragon/README.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

8 changes: 5 additions & 3 deletions install/kubernetes/tetragon/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -64,9 +64,11 @@ tetragon:
securityContext:
privileged: true
# -- Overrides the default livenessProbe for the tetragon container.
livenessProbe: {}
# grpc:
# port: 54321
livenessProbe:
timeoutSeconds: 60
httpGet:
path: "/liveness"
port: 6789

# Tetragon puts processes in an LRU cache. The cache is used to find ancestors
# for subsequently exec'ed processes.
Expand Down

0 comments on commit d9bd92c

Please sign in to comment.