-
Notifications
You must be signed in to change notification settings - Fork 20
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
[Request] Command line flag to force OpenShift #805
Comments
I guess this would be a flag (e.g. Maybe, for upstream, we can edit the |
I just meant something simpler than that. Just a cryostat-operator/internal/main.go Lines 212 to 214 in d7b0379
|
Ahh thanks I guess I was wondering what if |
I see, I think we should treat false as auto-discovery. We can call it |
Oh yea that would work better! Okay I can help with this today :D |
Thanks @tthvo! |
I think it could be valuable for troubleshooting purposes to be able to force oauth2_proxy use on OpenShift, which seems like it could be done with a similar or the same command line flag too. This way it isn't as directly exposed as a CR field, but it's still an available option. Right now if you're on OpenShift you can only get openshift-oauth-proxy, unless you edit the Operator sources and rebuild from that. |
Just closing and track the idea in #830 :D |
Describe the feature
It would be helpful for downstream releases if there was a command line option for the operator to force OpenShift instead of relying on the existing detection mechanism. Downstream releases for OpenShift won't have an OAuth2 proxy image available, only the OpenShift OAuth proxy. If the detection fails, this could result in a non-working installation.
The text was updated successfully, but these errors were encountered: