feat: Support custom manifests through the extraManifests value #870
+31
−0
Conversation
This file contains hidden or 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: elkh510 <[email protected]>
Signed-off-by: elkh510 <[email protected]>
elkh510
force-pushed
the
add_extra_manifests
branch
from
1b2ee87 to
445bbe8
Compare
Author
|
@stefangries hi |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 change introduces the extraManifests value, allowing users to provide and render arbitrary additional Kubernetes manifests as part of the chart deployment.
This enables injecting custom resources (such as ConfigMaps or any other Kubernetes objects) directly through values without modifying the chart itself.