feat: support setting priority class name for datahub pods #392
Conversation
This file contains 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
maggiehays
added
the
hacktoberfest-accepted
|
Each subchart needs a version increment and the main Chart.yaml's subchart versions should be incremented to match. Otherwise I have not issues with getting this merged, thanks! |
|
@david-leifker I have updated the chart and subchart versions. Also I didn't find any doc mentioning the chart version bump. requirement. If it is not mentioned anywhere else, can you mention it may be in the contrib readme? Thanks |
david-leifker
approved these changes
Nov 29, 2023
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.
This PR enables users to set required priority class name for datahub pods.
Checklist