[jbosstools-issues] [JBoss JIRA] (JBIDE-26919) OC binary: should warn if 3.x is used for an OpenShift 4 cluster (and vice versa)

[André Dietisheim (Jira)]

André Dietisheim created JBIDE-26919:
----------------------------------------

             Summary: OC binary: should warn if 3.x is used for an OpenShift 4 cluster (and vice versa)
                 Key: JBIDE-26919
                 URL: https://issues.jboss.org/browse/JBIDE-26919
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: openshift
    Affects Versions: 4.12.0.Final
            Reporter: André Dietisheim


OC 4.x does not fully work with an OpenShift 3.x cluster. The opposite is also true:

In a mail on the mailing list on the 17th of October (*[openshift-sme] 4.x oc client is not compatible with OCP 3.11.*)
{quote}
The open shift 4.1 CLI can't get SecurityContextConstraints from 3.11 openshift. Is this expected? or we need to fix this? 

# oc get SecurityContextConstraints restricted -o name
error: attempt to print an ungroupified object: /v1, Kind=SecurityContextConstraints

oc version
Client Version: version.Info{Major:"4", Minor:"1+", GitVersion:"v4.1.18-201909201915+53a7fbd-dirty", GitCommit:"53a7fbd", GitTreeState:"dirty", BuildDate:"2019-09-21T03:15:55Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"11+", GitVersion:"v1.11.0+d4cacc0", GitCommit:"d4cacc0", GitTreeState:"clean", BuildDate:"2019-09-12T23:41:09Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}
{quote}

answered by saying that one should use the oc binary that matches the cluster in terms of version:
{quote}
API's change per each OpenShift version. You should always be sure to match the version of the CLI to the target cluster version (at least to the minor version) and have experienced errors similar to what you are receiving in the past.
{quote}



--
This message was sent by Atlassian Jira
(v7.13.8#713008)