Skip to content

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

New issue
New issue
Closed
Closed
kubectl 1.5.1 vs k8s 1.6 gives error: no kind "Deployment" is registered for version "apps/v1beta1"#42392
Assignees
liggitt
Labels
kind/bugCategorizes issue or PR as related to a bug.priority/critical-urgentHighest priority. Must be actively worked on as someone's top priority right now.release-blockersig/api-machineryCategorizes an issue or PR as relevant to SIG API Machinery.sig/cliCategorizes an issue or PR as relevant to SIG CLI.
Milestone
v1.6

Description

@justinsb
justinsb
opened on Mar 2, 2017
>  ~/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"}

Activity

  1. justinsb
    added this to the v1.6 milestone on Mar 2, 2017
  2. justinsb
    added
    kind/bugCategorizes issue or PR as related to a bug.
    area/kubectl
    on Mar 2, 2017

  3. liggitt commented on Mar 2, 2017

    @liggitt
    liggitt
    on Mar 2, 2017
    Member

    prior to 1.6, kubectl cannot edit unknown kinds (fixed in #41304)

    you should be able to edit the deployment in the extensions group like ~/bin/kubectl-1.5.1 edit deployment.extensions -n kube-system dns-controller

  4. liggitt commented on Mar 2, 2017

    @liggitt
    liggitt
    on Mar 2, 2017
    Member

    @kubernetes/sig-cli-bugs

  5. justinsb commented on Mar 2, 2017

    @justinsb
    justinsb
    on Mar 2, 2017
    MemberAuthor

    ~/bin/kubectl-1.5.1 edit deployment.extensions -n kube-system dns-controller does work

    I don't know if this portends some other areas of incompatibility (get deployments works though). If not though, then if this is fixed in kubectl 1.6, then a release-note or similar to encourage people to upgrade kubectl seems like a reasonable fix (though we should then make sure that kubectl 1.6 works with older clusters!). Thanks @liggitt !

  6. liggitt commented on Mar 2, 2017

    @liggitt
    liggitt
    on Mar 2, 2017
    Member

    kubectl get was converted to read objects from the server in unstructured form before edit and apply were. The linked PR has release notes in it.

  7. 0xmichalis commented on Mar 3, 2017

    @0xmichalis
    0xmichalis
    on Mar 3, 2017
    Contributor

    @soltysh

  8. soltysh commented on Mar 3, 2017

    @soltysh
    soltysh
    on Mar 3, 2017
    Contributor

    Additionally k8s 1.6 will (hopefully) get the move where Deployments are additionally available under apps/v1beta1. Only newer kubectl like @liggitt mentioned will be able to handle this properly.

  9. pwittrock
    added
    sig/cliCategorizes an issue or PR as relevant to SIG CLI.
    on Mar 3, 2017

  10. pwittrock commented on Mar 5, 2017

    @pwittrock
    pwittrock
    on Mar 5, 2017
    Member

    @justinsb What is the bug to be fixed for 1.6?

  11. pwittrock
    added
    non-release-blocker
    on Mar 5, 2017

  12. justinsb commented on Mar 5, 2017

    @justinsb
    justinsb
    on Mar 5, 2017
    MemberAuthor

    @pwittrock not sure of the procedure in terms of tagging, but:

  13. pwittrock commented on Mar 5, 2017

    @pwittrock
    pwittrock
    on Mar 5, 2017
    Member

    @janetkuo Is this due to the Deployment version changing?

  14. pwittrock commented on Mar 5, 2017

    @pwittrock
    pwittrock
    on Mar 5, 2017
    Member

    #41656 is similar

  15. 40 remaining items

  16. pwittrock
    added
    priority/critical-urgentHighest priority. Must be actively worked on as someone's top priority right now.
    and removed
    non-release-blocker
    priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.
    on Mar 22, 2017
  17. liggitt
    added
    sig/api-machineryCategorizes an issue or PR as relevant to SIG API Machinery.
    on Mar 23, 2017
  18. bgrant0607
    assigned
    liggitt
    and unassigned
    soltysh
    on Mar 23, 2017
  19. k8s-github-robot
    closed this as completedin #43553on Mar 23, 2017
  20. k8s-github-robot
    added a commit that references this issue on Mar 23, 2017

    Merge pull request #43553 from liggitt/discovery-order

    b1e665f
  21. janetkuo
    added a commit that references this issue on Mar 23, 2017

    Remove the breaking change that's fixed

    0e3befb
  22. idvoretskyi
    added a commit that references this issue on Mar 24, 2017

    Remove the breaking change that's fixed

    81650d1
  23. mhan8796
    added a commit that references this issue on Jun 26, 2026

    Merge pull request kubernetes#43553 from liggitt/discovery-order

    dce965e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

kind/bugCategorizes issue or PR as related to a bug.priority/critical-urgentHighest priority. Must be actively worked on as someone's top priority right now.release-blockersig/api-machineryCategorizes an issue or PR as relevant to SIG API Machinery.sig/cliCategorizes an issue or PR as relevant to SIG CLI.

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions