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

feat: override priorityClassName from secrets-store-csi-driver subchart #943

Merged
merged 7 commits into from Jul 22, 2022

Conversation

jdweeks
Copy link
Contributor

@jdweeks jdweeks commented Jul 22, 2022

Reason for Change:

This PR adds the ability for end users of this chart to set the priorityClassName for pods created by the subchart secrets-store-csi-driver. This is useful to ensure that pods managed by the driver's DaemonSet are scheduled before application pods that depend on the driver.

The values for both linux and windows are already implemented in the subchart (secrets-store-csi-driver). We simply need to override / expose them here for end users of this chart.

Requirements

  • squashed commits
  • included documentation
  • added unit tests and e2e tests (if applicable).

Issue Fixed:

Does this change contain code from or inspired by another project?

  • Yes
  • No

If "Yes," did you notify that project's maintainers and provide attribution?

Special Notes for Reviewers:

Copy link
Member

@aramase aramase left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the PR!

Please update the yamls in the manifest_staging/ folder, where we host the staging charts and deployment yamls. All the yaml changes will then be promoted into the released charts folder with the next release.

@jdweeks jdweeks force-pushed the csi-driver-priorityClassName branch from c346475 to 79985b1 Compare July 22, 2022 18:59
@jdweeks
Copy link
Contributor Author

jdweeks commented Jul 22, 2022

Thank you for the PR!

Please update the yamls in the manifest_staging/ folder, where we host the staging charts and deployment yamls. All the yaml changes will then be promoted into the released charts folder with the next release.

done! thanks

@aramase
Copy link
Member

aramase commented Jul 22, 2022

/azp run pr-e2e

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@codecov-commenter
Copy link

Codecov Report

Merging #943 (79985b1) into master (d2e059f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #943   +/-   ##
=======================================
  Coverage   62.15%   62.15%           
=======================================
  Files           9        9           
  Lines         909      909           
=======================================
  Hits          565      565           
  Misses        311      311           
  Partials       33       33           

@aramase aramase merged commit 1ba0d55 into Azure:master Jul 22, 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

4 participants