Federated ReplicaSet

[aronchick]

Feature Description

• One-line feature description (can be used as a release note): Support ReplicaSets in Federation
• Primary contact (assignee): @perotinus
• Responsible SIGs: @kubernetes/sig-federation-feature-requests
• Design proposal link (community repo): https://github.com/kubernetes/community/blob/09ef55a496f8928573f7f4d2a8a38d0601737ddb/contributors/design-proposals/federated-replicasets.md
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @marun
• Approver (likely from SIG/area to which feature belongs): @madhusudancs
• Feature target (which target equals to which milestone):
  • Alpha release target (x.y): 1.5
  • Beta release target (x.y): 1.7

[ghost]

cc: @mwielgus Who's co-ordinating this effort.

[ghost]

@aronchick @goltermann could one of you please give me write access to this repo? I don't seem to be able to edit this issue.

[aronchick]

Done

On Mon, Aug 22, 2016 at 4:10 PM, Quinton Hoole notifications@github.com
wrote:

@aronchick https://github.com/aronchick @goltermann
https://github.com/goltermann could one of you please give me write
access to this repo? I don't seem to be able to edit this issue.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#46 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADIdcprR58OIMNiHNnUNocb8qrdQpC0ks5qiixegaJpZM4JTFNM
.

[janetkuo]

@quinton-hoole @mwielgus Are the docs ready? Please update the docs in https://github.com/kubernetes/kubernetes.github.io, and then add PR numbers and check the docs box in the issue description

[ghost]

Docs are being written. Should be available next week.

Q

On Fri, Sep 2, 2016 at 11:10 AM, Janet Kuo notifications@github.com wrote:

@quinton-hoole https://github.com/quinton-hoole @mwielgus
https://github.com/mwielgus Are the docs ready? Please update the docs
in https://github.com/kubernetes/kubernetes.github.io, and then add PR
numbers and check the docs box in the issue description

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#46 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ6NAXQMN3wMNTMxRFjzf0FDpweoTJegks5qmGacgaJpZM4JTFNM
.

[jaredbhatti]

@quinton-hoole Hey there, do you have a PR for the docs?

[ghost]

https://github.com/kelseyhightower/kubernetes-cluster-federation/blob/
master/labs/federated-nginx-service.md

@nikhiljindal is going to help to turn these into appropriate PR's

Q

On Wed, Sep 7, 2016 at 2:06 PM, Jared notifications@github.com wrote:

@quinton-hoole https://github.com/quinton-hoole Hey there, do you have
a PR for the docs?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#46 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ6NAboppv2lmruORR8H8Y1Bc7aVwJLKks5qnydqgaJpZM4JTFNM
.

[jaredbhatti]

@nikhiljindal Another ping on docs. Any PRs you can point me to?

[nikhiljindal]

Filed kubernetes/website#1215 for all federation docs

[ghost]

Released beta in v1.4

[madhusudancs]

Reopening this and assigning it to @perotinus (with me being a proxy).

[perotinus]

Before considering ReplicaSets beta, we need to address the issues in kubernetes/kubernetes#39986.

Also see https://docs.google.com/a/google.com/document/d/17u9arduSYPWYMvppxhzDXqUem3fM2mEA_1dvz97BlKI/edit?usp=sharing, which explains why weighting should remain an alpha feature for now and not block the progression to beta.

[idvoretskyi]

@madhusudancs @quinton-hoole I've updated the feature description to fit the new template. Please, fill the empty fields in the new template (their actual state was unclear).

[perotinus]

Feature Description

• One-line feature description (can be used as a release note): Support ReplicaSets in Federation
• Primary contact (assignee): @perotinus
• Responsible SIGs: @kubernetes/sig-federation-feature-requests
• Design proposal link (community repo): https://github.com/kubernetes/community/blob/09ef55a496f8928573f7f4d2a8a38d0601737ddb/contributors/design-proposals/federated-replicasets.md
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @marun
• Approver (likely from SIG/area to which feature belongs): @madhusudancs
• Feature target (which target equals to which milestone):
  • Alpha release target (x.y): 1.5
  • Beta release target (x.y): 1.7
  • Stable release target (x.y)

[grodrigues3]

Was this already beta as per this? It's unclear to me what's new in 1.7

[perotinus]

/unassign perotinus

I'm not working on deployments/replica sets at the moment.

[fejta-bot]

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

[fejta-bot]

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

[ghost]

The current implementation of Federated Replicasets will not be transitioned to Beta. There is a new API on the way. We'll open a separate feature to track that.