You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 and kube-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 (like node-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:
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: