HYPERFLEET-1123 - feat: define hyperfleet-critical PriorityClass and apply to maestro pods#51
HYPERFLEET-1123 - feat: define hyperfleet-critical PriorityClass and apply to maestro pods#51kuudori wants to merge 1 commit into
Conversation
…apply to maestro pods Add a cluster-scoped PriorityClass (value: 1000000000) to protect maestro infrastructure pods under resource pressure, and wire priorityClassName into all four maestro pod specs (server, agent, db, mqtt). - Add manifests/priority-classes.yaml with hyperfleet-critical PriorityClass - Add install-priority-classes Makefile target, hooked into install-all and install-all-rabbitmq before install-maestro - Set priorityClassName on all four maestro pods in umbrella values - Bump chart dependency versions to 0.1.1 for upstream priorityClassName hooks
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Important Review skippedAuto reviews are limited based on label configuration. 🚫 Review skipped — only excluded labels are configured. (2)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Central YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
|
PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Summary
hyperfleet-criticalPriorityClass (value: 1000000000) as a standalone manifest atmanifests/priority-classes.yamlinstall-priority-classesMakefile target, hooked intoinstall-allandinstall-all-rabbitmqbeforeinstall-maestropriorityClassName: hyperfleet-criticalinto all four maestro pod specs (server, agent, db, mqtt)priorityClassNamehooksVerification
Tested on local kind cluster:
make install-priority-classescreates the PriorityClass with correct valuekubectl get priorityclass hyperfleet-criticalreturns value=1000000000Test plan
make install-priority-classessucceedskubectl get priorityclass hyperfleet-criticalshows value below system-cluster-critical (2B)kubectl get pods -n maestro -o custom-columns=NAME:.metadata.name,PRIORITY_CLASS:.spec.priorityClassNameshowshyperfleet-criticalon all four pods