Skip to content

priorityclassname parameter for node-agent#6

Merged
apetruhin merged 1 commit intocoroot:mainfrom
gkalwig:feature/priorityclass
Apr 30, 2023
Merged

priorityclassname parameter for node-agent#6
apetruhin merged 1 commit intocoroot:mainfrom
gkalwig:feature/priorityclass

Conversation

@gkalwig
Copy link
Contributor

@gkalwig gkalwig commented Apr 14, 2023

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
Copy link

bmike78 commented Apr 28, 2023

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 apetruhin merged commit 814983e into coroot:main Apr 30, 2023
@apetruhin
Copy link
Member

@gkalwig, thank you for the contribution!

@bmike78
Copy link

bmike78 commented May 1, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants