helm-chart: add a way to easily set parameters for all backend pods #7148
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
Since backend pods are all fairly similar, it stands to reason that users would want to apply similar configuration to them. Add some `cvat.backend.*` parameters that are applied to all backend deployments/jobs.
SpecLad
force-pushed
the
backend-settings
branch
from
65c05a7
to
d470ba2
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #7148 +/- ##
===========================================
- Coverage 81.44% 81.43% -0.02%
===========================================
Files 364 364
Lines 39904 39904
Branches 3699 3699
===========================================
- Hits 32501 32496 -5
- Misses 7403 7408 +5
|
azhavoro
approved these changes
Nov 16, 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.
Motivation and context
Since backend pods are all fairly similar, it stands to reason that users would want to apply similar configuration to them. Add some
cvat.backend.*parameters that are applied to all backend deployments/jobs.How has this been tested?
Checklist
developbranch[ ] I have updated the documentation accordingly[ ] I have added tests to cover my changes[ ] I have linked related issues (see GitHub docs)[ ] I have increased versions of npm packages if it is necessary(cvat-canvas,
cvat-core,
cvat-data and
cvat-ui)
License
Feel free to contact the maintainers if that's a concern.