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.

Sign up for GitHub

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

Jump to bottom

Policy-based Federated Resource Placement #250

Closed
tsandall opened this issue Apr 17, 2017 · 10 comments
Closed

Policy-based Federated Resource Placement #250

tsandall opened this issue Apr 17, 2017 · 10 comments
Assignees
@tsandall
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status
Milestone
v1.7

Comments

@tsandall
Copy link

tsandall commented Apr 17, 2017 •
edited
Loading

Feature Description

  • One-line feature description (can be used as a release note): Policy-based control over Federated resource placement
  • Primary contact (assignee): @tsandall
  • Responsible SIGs: @kubernetes/sig-federation-feature-requests
  • Design proposal link (community repo): Proposal: policy-based federated resource placement community#292
  • Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @quinton-hoole @nikhiljindal
  • Approver (likely from SIG/area to which feature belongs): @nikhiljindal
  • Feature target (which target equals to which milestone):
    • Alpha release target (1.7)
    • Beta release target (TBD)
    • Stable release target (TBD)
@nikhiljindal nikhiljindal added the sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster. label Apr 17, 2017
@ghost
Copy link

ghost commented Apr 21, 2017

@tsandall This is targeted for v1.7 right? I've added that milestone.

@ghost ghost added this to the v1.7 milestone Apr 21, 2017
@tsandall
Copy link
Author

Yes, that's correct.

@ghost ghost assigned tsandall Apr 24, 2017
@ghost ghost added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Apr 24, 2017
@idvoretskyi idvoretskyi added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label May 3, 2017
@idvoretskyi idvoretskyi removed the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label May 18, 2017
@idvoretskyi
Copy link
Member

@tsandall please, provide us with the docs PR link (and update the features tracking spreadsheet with it).
/cc @kubernetes/sig-federation-feature-requests

@tsandall
Copy link
Author

kubernetes/website#4075

@uiansol
Copy link

uiansol commented Jul 17, 2017

From the tracking doc: "Need docs? yes"

I can help on this. What is needed @tsandall ?

@tsandall
Copy link
Author

@uiansol docs have been written for this already, see kubernetes/website#4075

@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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 31, 2017
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 30, 2018
@tsandall
Copy link
Author

@nikhiljindal is it safe to /close this now?

@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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

@tsandall tsandall

Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status
Projects
None yet
Milestone
v1.7
Development

No branches or pull requests
6 participants
@idvoretskyi @tsandall @uiansol @nikhiljindal @k8s-ci-robot @fejta-bot