Open buehlmann opened 3 years ago
It coud be use some RouteTemplate for Route security settings and has it at the operator global level rather than re-specify all possible Route options inside Infinispan CR
Also port.targetPort
is always static value 11222
and can't be changed
Indeed we don't need to specify the port. Imo it would be preferable that the operator manages all resources needed so that the deployment of Infinispan is kind of "self-contained" and I don't need to manage additional resources manually.
It would be great if the user could define more details of a OpenShift
Route
in the crd. In our case the following attributes would be required:annotations
(it seems to be already defined in the schema but not yet picked up by operator 2.0.4)port.targetPort
port.insecureEdgeTerminationPolicy
port.termination