Resource specs for Init Containers #428
Merged
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.
Implements #425
Motivation
As described in the FR some cluster providers are a little bit more "strict" regarding their deployed containers and the resources they are allowed to use. This patch introduces resources to all init containers together with a corresponding section in
values.yaml
Modifications
values.yaml
now has a new sectioninitContainer_resources
where each init container type is listed by name and describes the resources it is allowed to use.I also addedd a blank
resources
section topulsar_metadata
because the currently existing template uses this attribute, however there was no sign of it invalues.yaml
which is unintuitive.Verifying this change
(I don't know how, but lemme know how so I can run the checks)