Kops Create Master HA with 2 AZ AWS Singapore

[abdidarmawan007]

Hi all,can im set Kops create HA Master Kubernetes in singapore regions with only 2 AZ ?
Example like this
--zones=ap-southeast-1a,ap-southeast-1b --master-zones=ap-southeast-1a,ap-southeast-1b

[eedugon]

Please correct me if I'm wrong, but due to the nature of etcd clustering, which requires a quorum of at least 51% of the nodes up, you shouldn't even consider having 2 nodes, because if one of them goes down, the entire "master" cluster will go down (I guess). So, you should consider a minimum of 3 nodes in 3 AZs. I also feel it would be nice to have some basic HA for the masters with 2 nodes (active/passive for example), so if anyone knows a better (or the right) way to achieve this with kops let us know... About your specific question, I believe at this moment kops doesn't allow to create a cluster with 2 masters only, but I'm just a kops user, not a developer. Thanks!! El 29 jul. 2017 10:18 a. m., "Abdi Darmawan" <notifications@github.com> escribió:

…

Hi all,can im set Kops create HA Master Kubernetes in singapore regions with only 2 AZ ? Example like this --zones=ap-southeast-1a,ap-southeast-1b --master-zones=ap-southeast- 1a,ap-southeast-1b — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3088>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AYJbpcCHP-6XDMWuwsJc4sqLBIBJamn9ks5sSurVgaJpZM4OnS48> .

[msvbhat]

I agree with @eedugon, you shouldn't create a etcd cluster with 2 systems. It is better to have odd number of masters so that etcd cluster will have odd number of systems.

But for your case, you can specify --master-count=3 and --master-zones=ap-southeast-1a,ap-southeast-1b. I haven't tested this myself, but in theory it should work. (May not be advisable too, but should work ).

[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

[fejta-bot]

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