Allow creation of ingress in Openshift #701
Open
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.
Currently the chart will completely ignore the
server.ingress
block if the target deployment platform is OpenShift. As far as I can tell this was done to prevent accidental creation of two routes if bothserver.route
as well asserver.ingress
is enabled.However it can be helpful to also be able to deploy an
Ingress
on OpenShift, for example becausecert-manager
does not supportRoute
objects.With this PR there is the option to configure an
Ingress
, but we still keep as safeguard that a user doesn't accidentally create two routes.