-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Allow setting priorityClassName via helm chart #5255
Conversation
@Matthew-Beckett can I get your help reviewing this? 🙏🏼 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if that default empty string will still evaluate true on build unless commented out, need to test this properly in a cluster.
Update: docs say empty strings still evaluate false, will still test in cluster
@@ -33,6 +33,8 @@ podAnnotations: {} | |||
podSecurityContext: {} | |||
# fsGroup: 2000 | |||
|
|||
priorityClassName: "" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The if statement which evaluates if this is populated or not in deployment.yaml will evaluate to true and populate this invalid null string by default won't it?
Should this be commented out by default?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Never mind docs say empty strings evaluate false.
https://helm.sh/docs/chart_template_guide/control_structures/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TIL! So do you think this is good to merge?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm so sorry this has taken so long, I could make a whole load of excuses for the delay but none would make it okay.
I am so sorry @timbrd, thanks for your contribution ❤️
I've tested this now and I'm happy for merge!
Codecov Report
@@ Coverage Diff @@
## main #5255 +/- ##
=======================================
Coverage 72.38% 72.38%
=======================================
Files 30 30
Lines 1673 1673
Branches 367 367
=======================================
Hits 1211 1211
Misses 399 399
Partials 63 63 Continue to review full report at Codecov.
|
@jsjoeio @Matthew-Beckett Is there anything more which has to be done or will the PR land shortly? |
Based on that merge I'd say no... 😅 This is all ready to go! |
Adds an option to the helm chart to set a pod priority class.