Support OpenShift certificate serving used with TLS registry #1270
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.
Summary
Adding support for certificate serving so that we can test this section of the Quarkus TLS registry extension reference: https://quarkus.io/guides/tls-registry-reference#utilizing-openshift-serving-certificates
I have only implemented it for template-based builder. I think it should be technically possible to test this with extension-based builder, but probably need to configure Quarkus OpenShift extension specific properties inside of the test. It is not really relevant as I care about TLS registry reference verification ATM.
Regarding limitation to Quarkus runtime inside of this PR. I have added it so that I avoid (not necessarily) possible side-effects. I am just implementing what I need and if someone needs more, they need to extend functionality.
Please check the relevant options
run tests
phrase in comment)Checklist: