search

coroot / helm-charts

Coroot Helm charts
Apache License 2.0
18 stars 20 forks source link

priorityclassname parameter for node-agent #6

Closed gkalwig closed 1 year ago

gkalwig commented 1 year ago

By setting priorityClassName on a DaemonSet, you can assign a higher priority to the Pods managed by the DaemonSet, which ensures that they receive preferential treatment in resource allocation and scheduling. This can be especially important for critical system-level services that need to be highly available and responsive.

bmike78 commented 1 year ago

Running into this same issue on AWS hosted EKS clusters that limit number of pods per worker node. Having this priorityClassName in the helm chart would get around this issue.

apetruhin commented 1 year ago

@gkalwig, thank you for the contribution!

bmike78 commented 1 year ago

@gkalwig, also ran into this issue with pyroscope-ebpf.. PR here: https://github.com/pyroscope-io/helm-chart/pull/107