You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to use the ShinyProxy operator in an OpenShift cluster. I am able to get all pods running successfully and the ShinyProxy custom resources are working, however the real blocker seems to be with ingress and external access to the ShinyProxy services.
Do you have any recommendations on how to use the operator in OpenShift with the default HAProxy router?
The text was updated successfully, but these errors were encountered:
mkorejo
changed the title
OpenShift deployment support
OpenShift support
Jan 12, 2023
Hi, in general the operator should just work in OpenShift. To make the ingress work, you either have to point an existing ingress controller to the Skipper service or you can configure skipper as the main ingress controller.
However, with the recent release of the ShinyProxy Operator 2.0.0, there is no longer a need for Skipper. Therefore, it should be a lot easier to deploy the operator. The operator will automatically create ingress objects, which can be handled by any Kubernetes ingress controller
Hence, I would advise to checkout this new release. We are looking forward to any feedback!
I am trying to use the ShinyProxy operator in an OpenShift cluster. I am able to get all pods running successfully and the ShinyProxy custom resources are working, however the real blocker seems to be with ingress and external access to the ShinyProxy services.
Do you have any recommendations on how to use the operator in OpenShift with the default HAProxy router?
The text was updated successfully, but these errors were encountered: