Skip to content
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

Merged
merged 5 commits into from
Jul 18, 2022

Conversation

timbrd
Copy link

@timbrd timbrd commented Jun 10, 2022

Adds an option to the helm chart to set a pod priority class.

@jsjoeio
Copy link
Contributor

jsjoeio commented Jun 10, 2022

@Matthew-Beckett can I get your help reviewing this? 🙏🏼

Copy link
Contributor

@Matthew-Beckett Matthew-Beckett left a 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: ""
Copy link
Contributor

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?

Copy link
Contributor

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/

Copy link
Contributor

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?

Copy link
Contributor

@Matthew-Beckett Matthew-Beckett left a 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!

@jsjoeio jsjoeio enabled auto-merge (squash) June 23, 2022 17:42
@jsjoeio jsjoeio added this to the June 2022 milestone Jun 23, 2022
@codecov
Copy link

codecov bot commented Jun 23, 2022

Codecov Report

Merging #5255 (9ff3bf4) into main (19f486b) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           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.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 19f486b...9ff3bf4. Read the comment docs.

@jsjoeio jsjoeio modified the milestones: June 2022, July 2022 Jun 29, 2022
@timbrd
Copy link
Author

timbrd commented Jul 2, 2022

@jsjoeio @Matthew-Beckett Is there anything more which has to be done or will the PR land shortly?

@Matthew-Beckett
Copy link
Contributor

Matthew-Beckett commented Jul 2, 2022

@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!

@jsjoeio jsjoeio modified the milestones: July 2022, 4.5.1 Jul 18, 2022
@jsjoeio jsjoeio merged commit 530bb66 into coder:main Jul 18, 2022
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.

None yet

3 participants