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
Instead of the extension downloading the latest OKD release, it should check the OpenShift version and download the respective OKD/OCP version. This is specially important given the OKD/OCP 4 release.
Considering the above, version selection would not be needed for a large marjory of users and therefore should be hidden from the user. For example moved to something like "advanced config" that user can click to expand.
The text was updated successfully, but these errors were encountered:
On second thought this won't be so easy. To determine the version I need oc itself (unless one can somehow call a REST endpoint).
One could of course download the latest and use it to run oc version to then get the matching oc version. Not sure whether it is worth it. Maybe as additional option on the task ("match oc version").
OCP is yet another beast, since to my knowledge we don't have a publicly accessible URL for downloading OCP binaries. My understanding is that OKD and OCP oc versions are identical in matching versions (at least in terms of functionality).
We aren't actually doing any work in that area with OpenShift Online. We're pretty much in the same boat as everyone else with hoping that there is a better way to get those tools at some point :)
Instead of the extension downloading the latest OKD release, it should check the OpenShift version and download the respective OKD/OCP version. This is specially important given the OKD/OCP 4 release.
Considering the above, version selection would not be needed for a large marjory of users and therefore should be hidden from the user. For example moved to something like "advanced config" that user can click to expand.
The text was updated successfully, but these errors were encountered: