Simplify HA Setup for Master about enhancements HOT 27 CLOSED

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

from enhancements.

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.

from enhancements.

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

from enhancements.

@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?

from enhancements.

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, [email protected]
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
.

from enhancements.

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

from enhancements.

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

from enhancements.

@davidopp thinks this is unlikely to make it.

from enhancements.

Yeah, definitely not going to make it.

from enhancements.

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

from enhancements.

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

from enhancements.

This feature got an exception to merge the last bits after the code freeze and now is feature complete.

from enhancements.

Ping. Is there a docs PR for this?

from enhancements.

Docs PR is here: kubernetes/website#1810

from enhancements.

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

from enhancements.

nope nope, switching that back.

from enhancements.

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

from enhancements.

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

from enhancements.

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

from enhancements.

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

from enhancements.

@jszczepkowski that doc isn't public

from enhancements.

@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

from enhancements.

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#

from enhancements.

@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.

from enhancements.

@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.

from enhancements.

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

from enhancements.

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.

from enhancements.