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 finding it tricky to figure out the OpenShift server version whether it is 3.x or 4.x.
Right now the only thing we get is the server url from odo version/ oc version.
Why is this needed?
This will help for adapters to understand the server version and based on that decide the OpenShift web console URL.
For 3.x server, the web console URL does not use route and can be figured out using: {server_Url}/console.
But for 4.x server, the web console URL goes through routes using operators and can be determined using the following: oc get routes -n openshift-console -ojson | jq '.items[0].spec.host'
The text was updated successfully, but these errors were encountered:
If I remember correctly this was resolved on vs code plugin side already? @mohitsuman .
Closing for now, please re-open this issue if it's not yet resolved 🙂
[kind/Feature]
Which functionality do you think we should add?
I am finding it tricky to figure out the OpenShift server version whether it is
3.x
or4.x
.Right now the only thing we get is the server url from
odo version
/oc version
.Why is this needed?
This will help for adapters to understand the server version and based on that decide the OpenShift web console URL.
For 3.x server, the web console URL does not use route and can be figured out using:
{server_Url}/console
.But for 4.x server, the web console URL goes through routes using operators and can be determined using the following:
oc get routes -n openshift-console -ojson | jq '.items[0].spec.host'
The text was updated successfully, but these errors were encountered: