Closed ron1 closed 4 years ago
right now the operator requires routes, which are not available in Kubernetes. However it may be possible to add a flag to disable the route controller and use the rest of the functionalities in a Kubernetes instance.
Would it be possible on startup to only enable the route controller if the route api resource is available?
I think it should be possible, and this is a good idea.
Since most of the functionality of this operator is useful to the upstream Kubernetes community, consider making v0.0.3 available to both the OpenShift and upstream communities on OperatorHub.io.