As of today, Operator detects if running on OpenShift and only creates Routes in this case. Ingress are created instead when running on vanilla Kube. As of today you can configure certificates used by Ingress but Route just rely on default router/HAProxy ingress controller configuration in OpenShift.
We must provide a way to configure custom certs for OpenShift Routes. I see 2 ways of doing this :
Add a config flag that forces creation of Ingress instead of Route even if on OpenShift,
Add some OpenShift specific params that will allow to add specific PEM certificates and CA into Route objects.
These changes will require a bit of implementation time sand tests.
In a more "quick and easy-fix" fashion, we could also enable the injection of custom annotations on Routes (like we do on Ingress) so that Cert Utils operator (https://github.com/redhat-cop/cert-utils-operator) could do the job of injecting everything we need in Routes.
As of today, Operator detects if running on OpenShift and only creates
Routes
in this case.Ingress
are created instead when running on vanilla Kube. As of today you can configure certificates used byIngress
butRoute
just rely on default router/HAProxy ingress controller configuration in OpenShift.We must provide a way to configure custom certs for OpenShift
Routes
. I see 2 ways of doing this :These changes will require a bit of implementation time sand tests.
In a more "quick and easy-fix" fashion, we could also enable the injection of custom annotations on Routes (like we do on Ingress) so that Cert Utils operator (https://github.com/redhat-cop/cert-utils-operator) could do the job of injecting everything we need in Routes.