Skip to content

Commit

Permalink
[helm] Use grpc-based liveness probe
Browse files Browse the repository at this point in the history
The previous commit introduced a gRPC server 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:
tetragon:
  livenessProbe:
     timeoutSeconds: 60
     exec:
       command:
       - tetra
       - status
       - --server-address
       - "54321"
       - --retries
       - "5"

Signed-off-by: Anastasios Papagiannis <[email protected]>
  • Loading branch information
tpapagian committed May 29, 2024
1 parent bb83c16 commit 9ebe488
Showing 1 changed file with 4 additions and 9 deletions.
13 changes: 4 additions & 9 deletions install/kubernetes/tetragon/templates/_container_tetragon.tpl
Original file line number Diff line number Diff line change
Expand Up @@ -67,17 +67,12 @@
{{- if .Values.tetragon.livenessProbe }}
livenessProbe:
{{- toYaml .Values.tetragon.livenessProbe | nindent 4 }}
{{- else if .Values.tetragon.grpc.enabled }}
{{- else if .Values.tetragon.healthGrpc.enabled }}
livenessProbe:
timeoutSeconds: 60
exec:
command:
- tetra
- status
- --server-address
- {{ .Values.tetragon.grpc.address }}
- --retries
- "5"
grpc:
port: {{ .Values.tetragon.healthGrpc.port }}
service: "liveness"
{{- end -}}
{{- end -}}

0 comments on commit 9ebe488

Please sign in to comment.