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

Move federation out of core repo #5

Closed
irfanurrehman opened this issue Oct 27, 2017 · 4 comments
Closed

Move federation out of core repo #5

irfanurrehman opened this issue Oct 27, 2017 · 4 comments
Assignees
Labels
area/federation 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.

Comments

@irfanurrehman
Copy link
Contributor

Issue by shashidharatd
Monday Sep 25, 2017 at 14:57 GMT
Originally opened as kubernetes/kubernetes#52992


This issue is to track all the tasks associated with moving out federation related code out of core kubernetes repo into its own repo (k8s.io/federation).

Refer to the plan and discussion on moving out federation in this google doc

/cc @kubernetes/sig-federation-pr-reviews
/assign @irfanurrehman

@irfanurrehman irfanurrehman added area/federation 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. labels Oct 27, 2017
@irfanurrehman
Copy link
Contributor Author

Comment by shashidharatd
Tuesday Oct 10, 2017 at 17:25 GMT


/sig multicluster

@irfanurrehman
Copy link
Contributor Author

Comment by tengqm
Sunday Oct 22, 2017 at 08:05 GMT


/cc

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@shashidharatd
Copy link
Contributor

This task is complete, so closing.
/close

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/federation 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

4 participants