Simplify HA Setup for Master

[aronchick]

Description

Simplify setup for HA Master. Description in kubernetes/kubernetes#29649

Progress Tracker

• Before Alpha
  • Write and maintain draft quality doc
    • During development keep a doc up-to-date about the desired experience of the feature and how someone can try the feature in its current state. Think of it as the README of your new feature and a skeleton for the docs to be written before the Kubernetes release. Paste link to Google Doc: DOC-LINK
  • Design Approval
    • Design Proposal. This goes under docs/proposals. Doing a proposal as a PR allows line-by-line commenting from community, and creates the basis for later design documentation. Paste link to merged design proposal here: PROPOSAL-NUMBER
    • Initial API review (if API). Maybe same PR as design doc. PR-NUMBER
      • Any code that changes an API (/pkg/apis/...)
      • cc @kubernetes/api
    • Identify shepherd (your SIG lead and/or kubernetes-pm@googlegroups.com will be able to help you). My Shepherd is: replace.me@replaceme.com (and/or GH Handle)
      • A shepherd is an individual who will help acquaint you with the process of getting your feature into the repo, identify reviewers and provide feedback on the feature. They are not (necessarily) the code reviewer of the feature, or tech lead for the area.
      • The shepherd is not responsible for showing up to Kubernetes-PM meetings and/or communicating if the feature is on-track to make the release goals. That is still your responsibility.
    • Identify secondary/backup contact point. My Secondary Contact Point is: replace.me@replaceme.com (and/or GH Handle)
  • Write (code + tests + docs) then get them merged. ALL-PR-NUMBERS
    • Code needs to be disabled by default. Verified by code OWNERS
    • Minimal testing
    • Minimal docs
      • cc @kubernetes/docs on docs PR
      • cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
      • New apis: Glossary Section Item in the docs repo: kubernetes/kubernetes.github.io
    • Update release notes
• Before Beta
  • Testing is sufficient for beta
  • User docs with tutorials
    • Updated walkthrough / tutorial in the docs repo: kubernetes/kubernetes.github.io
    • cc @kubernetes/docs on docs PR
    • cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
  • Thorough API review
    • cc @kubernetes/api
• Before Stable
  • docs/proposals/foo.md moved to docs/design/foo.md
    • cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
  • Soak, load testing
  • detailed user docs and examples
    • cc @kubernetes/docs
    • cc @kubernetes/feature-reviewers on this issue to get approval before checking this off

FEATURE_STATUS is used for feature tracking and to be updated by @kubernetes/feature-reviewers.
FEATURE_STATUS: IN_DEVELOPMENT

More advice:

Design

• Once you get LGTM from a @kubernetes/feature-reviewers member, you can check this checkbox, and the reviewer will apply the "design-complete" label.

Coding

• Use as many PRs as you need. Write tests in the same or different PRs, as is convenient for you.
• As each PR is merged, add a comment to this issue referencing the PRs. Code goes in the http://github.com/kubernetes/kubernetes repository,
  and sometimes http://github.com/kubernetes/contrib, or other repos.
• When you are done with the code, apply the "code-complete" label.
• When the feature has user docs, please add a comment mentioning @kubernetes/feature-reviewers and they will
  check that the code matches the proposed feature and design, and that everything is done, and that there is adequate
  testing. They won't do detailed code review: that already happened when your PRs were reviewed.
  When that is done, you can check this box and the reviewer will apply the "code-complete" label.

Docs

• Write user docs and get them merged in.
• User docs go into http://github.com/kubernetes/kubernetes.github.io.
• When the feature has user docs, please add a comment mentioning @kubernetes/docs.
• When you get LGTM, you can check this checkbox, and the reviewer will apply the "docs-complete" label.

[idvoretskyi]

cc @kubernetes/sig-cluster-lifecycle @sig-clusterops

[timothysc]

What exactly are we aiming to do here? We haven't cited the series of issues that @mikedanese and I created a while ago and the description doesn't exist.

[fgrzadkowski]

The idea is to automate setting up HA master in OSS. We will use kube-up.sh for GCE for that.

[philips]

@timothysc can you gather up those issues and we can update the issue body?

@fgrzadkowski can you and @jszczepkowski work to create a more useful body?

[errordeveloper]

Yes, please, it would be great to see it all in one place. Also, lately I
had been thinking about what HA control plane bootstrap/discovery API could
look like.

On Tue, 26 Jul 2016, 23:58 Brandon Philips, notifications@github.com
wrote:

@timothysc https://github.com/timothysc can you gather up those issues
and we can update the issue body?

@fgrzadkowski https://github.com/fgrzadkowski can you and @jszczepkowski
https://github.com/jszczepkowski work to create a more useful body?

—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
#48 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPWS9uZ1w56419trvVWG4Tbh0OqlRPtks5qZpEhgaJpZM4JTH5P
.

[fgrzadkowski]

I've just sent PR with design for this feature in kubernetes/kubernetes#29649. Please see what's missing.

[timothysc]

All backlog'd items have been labeled: https://github.com/kubernetes/kubernetes/labels/area%2FHA

[alex-mohr]

@davidopp thinks this is unlikely to make it.

[davidopp]

Yeah, definitely not going to make it.

[idvoretskyi]

@jszczepkowski @alex-mohr @davidopp is this feature actively developed? Can we expect it to be present in 1.5?

[fgrzadkowski]

Yes it is actively developed. We should make it for 1.5.

[jaredbhatti]

Ping. Is there a docs PR for this?

[jszczepkowski]

Docs PR is here: kubernetes/website#1810

[spiffxp]

I'm removing the team/SIG-ClusterLifecycle label given that SIG-ClusterOps is listed as the owner in the 1.5 feature spreadsheet; if we're using labels to describe areas of overlap then we need something else in these issues to identify owner

[timothysc]

nope nope, switching that back.

[jszczepkowski]

I've created a doc describing potential etcd/master replica failure scenarios that shall be manually tested. Everybody is invited to review it.

[idvoretskyi]

@aronchick @jszczepkowski can you confirm that this item targets beta in 1.6?

[idvoretskyi]

@aronchick @jszczepkowski any progress for 1.7 is expected for this feature?

[timothysc]

We will write an updated proposal for kubeadm deployments in the 1.7 cycle.
/cc @kubernetes/sig-cluster-lifecycle-misc

[philips]

@jszczepkowski that doc isn't public

[philips]

@timothysc please add me on any proposal. I really think that a self-hosted etcd model using the etcd Operator here can address a number of the concerns and simplify the deployment, maintenance, and failure-domain burden for the user.

For example see my demos from KubeCon

cc @hongchaodeng @xiang90

[timothysc]

There is a draft up for comment, and we'll hash out a more formal proposal with the SIG.

https://docs.google.com/document/d/1lH9OKkFZMSqXCApmSXemEDuy9qlINdm5MfWWGrK3JYc/edit#

[apsinha]

@jbeda is SIG lifecycle targeting this feature for 1.7? It is not in the features repo but perhaps was part of your SIG's planning so PM SIG wanted to check in.

[timothysc]

@apsinha We're planning to complete our draft proposal and might begin execution on some elements, but we are not delivering a full solution for this cycle.

[luxas]

@roberthbailey should we close this in favor for the more specialized #357?
This seems more GCE-specific...

[roberthbailey]

I agree. This feature was to track adding HA support to kube-up.sh. That is done, but since kube-up is deprecated we aren't planning to graduate the implementation beyond it's current support level.