disable ingress by default - #15
Merged
Merged
Conversation
wafschneider
approved these changes
Aug 3, 2026
wafschneider
left a comment
wafschneider
left a comment
Contributor
There was a problem hiding this comment.
I agree with this change. @david-igbinedion let us know what you think, and then can you please make a new release!
Collaborator
|
I agree as well |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
By default, the helm chart creates an ingress even if the ingress configuration is not specified. The default configuration is meant to be a template which specifies the host 'xyz.hostname-of-your-service.com'. Creating this ingress is pointless. Therefore, the helm chart default value for ingress.enabled should be 'false'.