fix(helm): start PostgreSQL without gosu on K3s

This commit is contained in:
王野 committed 2026-11-10 14:52:07 +08:00
1 parent 60356c55aa
commit 88ebfd30e1
7 files changed
+124

No files matched your search

@@ -207,6 +207,11 @@ spec:
labels:
app.kubernetes.io/component: {{ $name }}-postgres
spec:
securityContext:
# Run the image entrypoint as postgres so it does not invoke gosu.
runAsUser: 999
runAsGroup: 999
fsGroup: 999
{{ include "mixingx-unit.followerScheduling" . | nindent 6 }}
{{- with $.Values.imagePullSecrets }}
imagePullSecrets:
@@ -216,6 +221,10 @@ spec:
- name: postgres
image: {{ .Values.images.postgres.repository }}:{{ .Values.images.postgres.tag | default "latest" }}
imagePullPolicy: IfNotPresent
command: ["docker-entrypoint.sh", "postgres"]
securityContext:
# Temporary compatibility workaround for checkpoint signal failures on affected k3s nodes.
privileged: true
env:
- name: POSTGRES_PASSWORD
value: "{{ .Values.sharedInfra.postgres.password }}"
@@ -229,6 +238,15 @@ spec:
- name: tcp
containerPort: {{ .Values.ports.postgres }}
protocol: TCP
readinessProbe:
exec:
command:
- sh
- -ec
- >-
exec pg_isready -q -h 127.0.0.1 -p {{ .Values.ports.postgres }} -U "$POSTGRES_USER" -d "$POSTGRES_DB"
periodSeconds: 5
timeoutSeconds: 3
volumeMounts:
- name: data
mountPath: /var/lib/postgresql/data