根因(dotnet/runtime#136603,已由同事在 sciveda 现场实测验证):Ubuntu 26.04 新内核 配套 AppArmor 行为禁止容器内进程向自身线程发信号(pthread_kill/tgkill → EACCES), CoreCLR GC 挂起线程失败 → 运行时 abort → dmesg 表现为 'general protection fault in libc.so.6[+0x289a2]'(.NET BGC/Server GC/TP Worker 线程),容器 exit 139 CrashLoop,负载越高崩得越频,且 journalctl 无 apparmor=DENIED 记录。 同机制亦解释此前 postgres 'could not signal for checkpoint: Permission denied' (privileged 之所以有效 = privileged 容器不受 AppArmor 约束)。 修复:agent/sso/ultra/edge/gateway/platform 六处 .NET 主容器 securityContext.appArmorProfile.type: Unconfined。
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