Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenShift support #38

Open
mkorejo opened this issue Jan 12, 2023 · 1 comment
Open

OpenShift support #38

mkorejo opened this issue Jan 12, 2023 · 1 comment
Labels
question Further information is requested

Comments

@mkorejo
Copy link

mkorejo commented Jan 12, 2023

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?

@mkorejo mkorejo changed the title OpenShift deployment support OpenShift support Jan 12, 2023
@LEDfan
Copy link
Member

LEDfan commented Mar 6, 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!

@LEDfan LEDfan added the question Further information is requested label Mar 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants