Conversation
Add optional priorityClassName to all 5 Deployment workloads (kubescape, kubevuln, operator, prometheus-exporter, storage) using a shared helper template with customScheduling fallback, consistent with the existing nodeSelector/affinity/tolerations pattern. Signed-off-by: bl4ko <gasperoblak@bl4ko.com>
…rage Signed-off-by: Matthias Bertschy <matthias.bertschy@gmail.com>
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (14)
📝 WalkthroughWalkthroughThe pull request introduces priorityClassName scheduling support to the kubescape-operator Helm chart by adding a reusable helper template function and integrating it across multiple component deployments and cronjobs, along with corresponding configuration values. Changes
Poem
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
replacing #804
Summary by CodeRabbit
customScheduling.priorityClassNameor override per-component (kubescape, operator, kubevuln, storage, synchronizer, node-agent, and others) via new Helm chart values, enabling fine-grained control over pod scheduling priorities.