agent-platform release v4.131.1

Changed

• The Substrate workers run above the default priority: PriorityClass agent-platform-worker-pool (giantswarm/agent-platform#999). The WorkerPool’s worker pods carried no class and ran at priority 0, so atelet’s ate-node-critical (PreemptLowerPriority) evicted a worker, and its actor with it, among the first pods of a full node. The connectivity chart renders the class kagent.substrateWorkerPool.priorityClass names (value 1000000: above 0, below the cluster’s monitoring, platform and atelet classes; preemptionPolicy: Never, not the global default), and the meta chart derives the pool’s template.priorityClassName from it; the ordinary workloads at 0 are evicted first. An installation’s own template.priorityClassName stands; enabled: false renders no class and names none; a value outside 1..999999999 or a system- name fails the render. The upgrade rolls the pool’s workers once, one at a time under the worker budget. make verify-workerpool asserts the class, the derived name and the guards.