Description of problem:
API server can't recognize Route and DeploymentConfig resources when we run `oc set env` command with `--local=false`.
Version-Release number of selected component (if applicable):
4.14
How reproducible:
100%
Steps to Reproduce:
$ oc apply -f process.json
./oc414 set env -e FOO="BAR" -f process.json --local=false -o json
unable to recognize no matches for kind "Route" in version "v1"
unable to recognize no matches for kind "DeploymentConfig" in version "v1"
The same command works well with OC cli 4.10
./oc410 set env -e FOO="BAR" -f process.json --local=false -o json
W0411 21:53:46.214928 150136 shim_kubectl.go:58] Using non-groupfied API resources is deprecated and will be removed in a future release, update apiVersion to "route.openshift.io/v1" for your resource
W0411 21:53:46.218480 150136 shim_kubectl.go:58] Using non-groupfied API resources is deprecated and will be removed in a future release, update apiVersion to "apps.openshift.io/v1" for your resource
Warning: apps.openshift.io/v1 DeploymentConfig is deprecated in v4.14+, unavailable in v4.10000+
{
"kind": "Service",
"apiVersion": "v1"
......
......
Actual results:
The `oc set env -e FOO="BAR" -f process.json --local=false -o json` not working.
Expected results:
The `oc set env -e FOO="BAR" -f process.json --local=false -o json` should work the same way it works for 4.10 version of OC CLI.
Additional info:
- is related to
-
OCPBUGS-32108 `oc set env` command changes apiVersion for route and deploymentconfig
-
- New
-
