根因:官方 postgres:17 镜像(2026-08 构建)内 gosu 在新内核(Ubuntu 26.04 kernel 7.0.0-39+)上 用户态死循环,容器假活(Running 但 5432 无服务、PGDATA 空、零日志);绕过 gosu 后 PG17 恢复期 signal checkpoint 再遇权限死循环,故三件缺一不可: - pod securityContext: runAsUser/runAsGroup/fsGroup=999(以 postgres 用户直跑,跳过 gosu) - container command: docker-entrypoint.sh postgres(非 root 下 entrypoint 自动跳过 gosu) - container securityContext: privileged(否则恢复期 'could not signal for checkpoint: Permission denied') 涉及 5 个模板:sso/ultra/audit(audit-db)/platform(audit)/agent-unit 各自内嵌的 postgres。 实测:xjf1641(Xeon+kernel43)与 wytest(i5+kernel42)原始定义必死、打补丁后稳定运行; kernel 7.0.0-38 老机(如 184)暂未触发但同机制不免疫,升级内核前必须先吃本修复。
MixingX Agent Unit Chart
Deploys one agent site as one Helm release:
agent-<site>backendagent-web-<site>frontendagent-<site>-postgresStatefulSet and retained PVC
The release requires a pre-created PostgreSQL credentials Secret. By default its
name is agent-<site>-postgres-credentials; the required keys are
admin-password, app-password, and connection-string. The Agent connection
string must use sharedInfra.postgres.appUsername, while the init container uses
the administrator credential only to idempotently provision the non-superuser
application role and its database-local idle transaction timeout.
Example:
helm upgrade --install mixingx-agent-workshop-a ./charts/mixingx-agent-unit \
--namespace mixingx --create-namespace \
--set site=workshop-a \
--set nodeName=agent-node-01 \
--set storage.className=longhorn \
--set sharedInfra.postgres.appUsername=agent_workshop_a \
--set tag=2026.07.02-abc1234