Separate ingress.usedefault from .enable #139
Closed
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 allows ingress.enabled to create the ingress object for
use with another ingress controller.
used in conjunction with ingress.useDefault=false,
coderd.devurlsHost, and ingress.host to get the full ingress experience
Note that I tried setting coderd.serviceNext explicitly to false but it only looks for true. Not sure if we want that to be an either-way override or just a force-to-next or ignore mechanism as it is now.