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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https
here is added to the internal keystone endpoint: if tls is not enabled at Pod level (podLevel: true
in the ctlplane) but the ingress is configured as an edge router [1] this will fail.While I think https should be the default, we should isolate the prefix in it's own variable.
I'm ok to follow up on that, but I would try something like:
so we can make it configurable w/o introducing extra complexity.
[1] https://www.redhat.com/architect/encryption-secure-routes-openshift
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
However, considering you can override the entire variable, my comment is not a blocker for the patch, more of a consideration.
So let me know if you want to keep it as it is and I can approve.