Files
OpenShell/deploy
Bryce Wilkinson 69ec36a68f feat(helm): expose priorityClassName and topologySpreadConstraints
The gateway pod template exposes nodeSelector, affinity and tolerations but
not priorityClassName or topologySpreadConstraints. Operators who need
either have to fork the chart or mutate the rendered output out-of-band.

Add two optional passthroughs:

- priorityClassName: the gateway is a control-plane component. When it shares
  nodes with the workloads it serves, the default priority gives it no
  advantage under node pressure, so a local capacity crunch can evict it and
  widen into a fleet-wide outage.
- topologySpreadConstraints: spread replicas across zones or nodes. Only
  affinity was available, which is a blunter tool for even spreading.

Both go in the shared gatewayPodTemplate, so they apply identically to the
statefulset and deployment workload shapes. Both render only when set; a
default render is byte-identical to before this change.

The data volume size/StorageClass passthroughs from the original revision are
dropped: upstream now provides them as server.dataStorageSize and
server.dataStorageClass.

Signed-off-by: Bryce Wilkinson <22760097+bjw123@users.noreply.github.com>
2026-10-22 14:16:41 +03:00
..