-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use PriorityClass #322
Labels
Comments
Bezbran
added
good first issue
Good for newcomers
enhancement
New feature or request
labels
Oct 31, 2023
It would be nice to be able to set up the priorityclass on the helm chart values. like this chart for example |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview
Kubernetes offers a feature called PriorityClass which empowers cluster operators to determine the relative priority of pods. For our setup, pods such as the
node-agent
daemonset andkube-vuln
should inherently possess a higher priority compared to other application pods.Issue
Currently, the absence of a defined
PriorityClass
for our pods results in certain pods (likenode-agent
,kube-vuln
, etc.) lingering in the "Pending" state. This persists until a cluster operator intervenes by manually deleting pods from nodes.Proposed Solution
We should leverage
PriorityClasses
to address this:system-node-critical: This should be assigned to
node-agent
pods, ensuring they run on every node without exception.system-cluster-critical: This is apt for the remaining pods (
operator
,kubescape
,kube-vuln
, etc.) as they are essential for maintaining the cluster's health.The text was updated successfully, but these errors were encountered: