Repository navigation
feat(operator): configure auxiliary resources and management placement - #762
Conversation
…cement Signed-off-by: Baylem <zelathis@gmail.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 38 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Signed-off-by: Baylem <zelathis@gmail.com>
Signed-off-by: Baylem <zelathis@gmail.com>
Signed-off-by: Baylem <zelathis@gmail.com>
Signed-off-by: Baylem <zelathis@gmail.com>
Signed-off-by: Baylem <zelathis@gmail.com>
Signed-off-by: Baylem <zelathis@gmail.com>
Signed-off-by: Baylem <zelathis@gmail.com>
|
Hey, thanks for this one. I'm fine with the new default resource requests, and with game pods rolling once on upgrade. One thing I don't want: Could you change it so the chart handles it instead? For example, turn leader election on automatically when replicas > 1, or keep rendering and print a clear warning in While you're there, it would make review easier if the operator Recreate migration Job and the PDBs went into their own PR, since they're not really part of "auxiliary resources and placement". Thanks! |
Signed-off-by: Baylem <zelathis@gmail.com>
|
Addressed in 6d8d42c. Removed the upgrade failure. When operator.replicas is greater than one, the chart now enables leader election automatically and renders RollingUpdate even if saved values contain leaderElect: false. NOTES.txt explains the effective setting, the singleton Recreate migration hook is skipped for that case, and the release notes plus chart checks cover old values and --reuse-values. I retained the optional PDBs and singleton migration hook in this revision. #724 explicitly requested the PDBs with placement; the hook is coupled to the retained Recreate strategy because Helm server-side apply cannot clear the old defaulted RollingUpdate fields by itself. Moving the hook without that strategy change would break the singleton upgrade path. This keeps those dependencies intact without rewriting the shared PR stack. The chart check source compiles; Helm/runtime regression execution remains in CI. |
Signed-off-by: Baylem <zelathis@gmail.com>
Generated auxiliary containers had no consistent resource reservations, and management Deployments lacked a common placement/disruption configuration.
Add configurable requests for agents/config init, sentinels, tunnel relays and restic workers through operator flags and Helm. Explicit resource objects replace defaults, including an empty object to clear them. Add placement fields and optional PDBs for management Deployments, require leader election for multiple operator replicas, and document a management/game worker layout and upgrade behavior.
A scoped pre-upgrade hook clears server-defaulted rollingUpdate fields before applying Recreate to an existing operator with leader election disabled. It also works when CRDs are managed externally. The hook supports maximum-length Helm release names, and re-enabling leader election explicitly restores RollingUpdate.
Closes #724.
Validation:
Defaults are starting resource reservations, with no new CPU/memory limits; deployment measurements should guide tuning. Existing workloads may restart or become Pending as requests are applied. Keep the HostPort placement changes from #761 and the Cilium option from the network-isolation PR when resolving shared CI/controller files. API singleton lifecycle changes remain in #758. Web/Compose image builds on this base need #759.