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
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Dependency update
[ ] Refactoring
[ ] Release (follows conventions described in the RELEASE.md)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] This change requires a documentation update
[x] This change requires execution against OCP (use run tests phrase in comment)
Checklist:
[x] Example scenarios has been updated / added
[x] Methods and classes used in PR scenarios are meaningful
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: