根因:官方 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。 同内容已提交 develop 分支 407aef8;实测:xjf1641(Xeon+kernel43)与 wytest(i5+kernel42) 原始定义必死、打补丁后稳定;kernel 7.0.0-38 老机暂未触发但不免疫,升级内核前必须先吃本修复。
MixingX Platform Chart
This chart owns central MixingX services only:
gatewayssoandsso-webultraandultra-webaudit- shared
redis,mongo, andrabbitmq - platform ingress and Gateway RBAC
It intentionally does not render edge or agent instances. Customer or site-specific instances should be deployed with mixingx-edge-unit and mixingx-agent-unit as separate Helm releases or Argo CD Applications.
Use this boundary so platform upgrades cannot prune customer-added edge/agent instances.