Adding additionalConfig for bootstrap pods #356
Merged
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
Signed-off-by: Luis Schweigard <luis.schweigard@maibornwolff.de>
lieberlois
force-pushed
the
additional-bootstrap-config
branch
from
f09a73f
to
5c43ef9
Compare
idanl21
approved these changes
Nov 9, 2022
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 pullrequest adds functionality for configuring an additionalConfig for bootstrap pods and fixes #296
The implementation defaults the additionalConfig of the bootstrap pod to
spec.general.additionalConfigand overwrites themap[string]stringwithspec.bootstrap.additionalConfigwhen set.