kubernetes: kubectl 1.5.1 vs k8s 1.6 gives `error: no kind "Deployment" is registered for version "apps/v1beta1"`

>  ~/bin/kubectl-1.5.1 edit deployment -n kube-system dns-controller
error: no kind "Deployment" is registered for version "apps/v1beta1"

> ~/bin/kubectl-1.5.1 version
Client Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.1", GitCommit:"82450d03cb057bab0950214ef122b67c83fb11df", GitTreeState:"clean", BuildDate:"2016-12-14T00:57:05Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"7+", GitVersion:"v1.7.0-alpha.0.661+01bfbb5fa04621", GitCommit:"01bfbb5fa0462189932b704be32401822a991627", GitTreeState:"clean", BuildDate:"2017-03-02T01:45:33Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 1
Comments: 39 (35 by maintainers)

Commits related to this issue

Fixes #42392. Prefer extensions group over apps group. Kubectl 1.5 still uses compiled in types in kubectl edit and apply. Because kubectl 1.5 does not have the apps/v1beta1/deployment resource comp... — committed to pwittrock/kubernetes by pwittrock 7 years ago
Merge pull request #43553 from liggitt/discovery-order Automatic merge from submit-queue Preserve API group order in discovery, prefer extensions over apps Fixes #42392, supercedes #43543 Kubect... — committed to kubernetes/kubernetes by deleted user 7 years ago
Remove the breaking change that's fixed https://github.com/kubernetes/kubernetes/issues/42392 is fixed — committed to kubernetes/enhancements by janetkuo 7 years ago
Remove the breaking change that's fixed https://github.com/kubernetes/kubernetes/issues/42392 is fixed — committed to kubernetes/enhancements by janetkuo 7 years ago
Prefer apps version over deprecated extensions Due to backwards compatibility issues (https://github.com/kubernetes/kubernetes/issues/42392) introduced in 1.6 when adding new API group we've set exte... — committed to soltysh/kubernetes by soltysh 4 years ago

Most upvoted comments

@liggitt @fabianofranz @AdoHe Perhaps we need to revisit out commitment to supporting skewed / client server. We consistently fail to meet this commitment, and I would rather tell users they need to match the client / server version than have things break when we tell them that client / server version skew is supported. WDYT?

@pwittrock probably needs broader discussion but I’d be in favor. You’d still support skew of point releases (e.g. kubectl 1.6.1 --> server 1.6.0, etc)?

fabianofranz on Mar 8, 2017