Skip to content
This repository has been archived by the owner on Apr 21, 2019. It is now read-only.

kubefed should use an API version that both it and server uses #27

Jump to bottom
Jump to bottom
Closed
Closed
kubefed should use an API version that both it and server uses#27
Labels
area/federationkind/bugCategorizes issue or PR as related to a bug.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/multiclusterCategorizes an issue or PR as relevant to sig-multicluster.
@irfanurrehman

Description

@irfanurrehman
irfanurrehman
opened on Oct 30, 2017

Issue by nikhiljindal
Friday Aug 11, 2017 at 23:57 GMT
Originally opened as kubernetes/kubernetes#50540

Forked from kubernetes/kubernetes#50534 (comment).

kubefed does API version discovery and then uses the preferred API group version that server supports. This breaks when server supports a newer version that the generated clientset that kubefed uses does not know about.
kubefed should choose the version that both server and it knows about.

kubernetes/kubernetes#50537 fixes this for RBAC. We need the same for all API resources that kubefed creates.

cc @kubernetes/sig-federation-bugs @liggitt

Metadata

Assignees

No one assigned

    Labels

    area/federationkind/bugCategorizes issue or PR as related to a bug.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/multiclusterCategorizes an issue or PR as relevant to sig-multicluster.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions