Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking the deprecation of Fedv1 API #13905

Closed
jimangel opened this issue Apr 20, 2019 · 6 comments
Closed

Tracking the deprecation of Fedv1 API #13905

jimangel opened this issue Apr 20, 2019 · 6 comments
Assignees
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster.
Milestone

Comments

@jimangel
Copy link
Member

jimangel commented Apr 20, 2019

Federation v1 has been deprecated in favor of Federation v2. I have worked with #sig-multicluster to come up with a plan to phase out the old and bring in the new.

I'm opening this issue to track deprecating the Federation v1 generation docs

Out of scope, to be left alone and updated by #sig-multicluster before EOY 2019

Background (from #sig-multicluster slack):

irfanurrehman [3 days ago]
https://kubernetes.io/docs/concepts/cluster-administration/federation/
and pages at https://kubernetes.io/docs/tasks/federation/ can be retained until we are up with new placeholder page(s) (positively before kubecon)

jimangel [2 days ago]
@marun @irfanurrehman let me know if there's lazy consensus after today's meeting and I will work to remove to generated docs / document. It will be up to someone in #sig-multicluster to work on the fedv2 content. If there's any questions on the style guide or placement - there's always tons of people willing to help in #sig-docs.

irfanurrehman [2 days ago]
Hi @jimangel there seems to be consensus on the steps we talked about, in today's meeting. However few stakeholders were absent. As far as I understand this is targeted towards 1.15 release so we seem to have time.

irfanurrehman [2 days ago]
Lets delay going ahead with removing the api-docs by 1 more week and I will report back to you next week if you can go ahead with it.

Wait until after Friday 4/26/19 before taking any action, but I could use some help cleaning this up if anyone is interested!

@jimangel jimangel added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Apr 20, 2019
@jimangel jimangel added this to the 1.15 milestone Apr 20, 2019
@jimangel jimangel self-assigned this Apr 20, 2019
@thecrudge
Copy link
Contributor

/assign @thecrudge

@irfanurrehman
Copy link
Contributor

@jimangel There is consensus on the steps that you mentioned. Thanks for taking this up.

@irfanurrehman
Copy link
Contributor

cc @kubernetes/sig-multicluster-misc

@k8s-ci-robot k8s-ci-robot added the sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster. label May 2, 2019
@thecrudge
Copy link
Contributor

Updated PR #14140

@claurence
Copy link

@jimangel - this PR has the 1.15 milestone on it - is it expected to merge or this release? The docs last call milestone is today

@jimangel
Copy link
Member Author

Just merged the federation changes, thanks @thecrudge! Great work!
/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster.
Projects
None yet
Development

No branches or pull requests

5 participants