根因(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 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.