priorityclassname parameter for node-agent #6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
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
approved these changes
Apr 30, 2023
|
@gkalwig, thank you for the contribution! |
|
@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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.