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.

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

Create one nodes instance group per zone #9471

Merged
merged 3 commits into from
Jul 17, 2020

Conversation

johngmyers
Copy link
Member

@johngmyers johngmyers commented Jul 1, 2020

Creates one nodes instance group per zone, restricted to that zone. Changes the default number of nodes to the number of zones. If fewer nodes than zones, only creates one instance group per node.

Fixes #8152

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. area/documentation labels Jul 1, 2020
@hakman
Copy link
Member

hakman commented Jul 2, 2020

If fewer nodes than zones, only creates one instance group per node.

I would go with changing what number of nodes means and applying it to each instance group.

@olemarkus
Copy link
Member

I would also change the meaning of node-count to be number of nodes per AZ. Isn't that what happens as the implementation is exactly now?

@hakman
Copy link
Member

hakman commented Jul 2, 2020

@olemarkus at the moment an ASG can span multiple AZs so, you just set a fixed number of nodes that are randomly assigned to an AZ.

@olemarkus
Copy link
Member

Sorry, I missed a change in new_cluster.go.

I would either change this to nodes per AZ or documenting that this is the total number of nodes in the cluster. If we go for nodecount remaining the total number of nodes in the cluster, how we distribute the nodes across zones should be mentioned in the docs too.

@johngmyers
Copy link
Member Author

--master-count is the total number of master nodes, not the number of master nodes per IG. Making --nodes-count be the number of nodes per IG would be inconsistent.

The documentation says "Set number of nodes. Defaults to one node per zone", which is precisely the behavior implemented.

@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jul 3, 2020
@johngmyers johngmyers changed the title WIP Create one nodes instance group per zone Create one nodes instance group per zone Jul 3, 2020
@k8s-ci-robot k8s-ci-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels Jul 3, 2020
@k8s-ci-robot k8s-ci-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Jul 7, 2020
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 8, 2020
cmd/kops/create_cluster.go Outdated Show resolved Hide resolved
@hakman
Copy link
Member

hakman commented Jul 17, 2020

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 17, 2020
@hakman
Copy link
Member

hakman commented Jul 17, 2020

/retest

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 17, 2020
@rdrgmnzs
Copy link
Contributor

Thanks @johngmyers !

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 17, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: johngmyers, rdrgmnzs

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 17, 2020
@k8s-ci-robot k8s-ci-robot merged commit 022fec8 into kubernetes:master Jul 17, 2020
@k8s-ci-robot k8s-ci-robot added this to the v1.19 milestone Jul 17, 2020
@johngmyers johngmyers deleted the ig-per-zone branch July 17, 2020 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/documentation cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Proposal: Have new multi-zone AWS clusters create node instance groups per zone
6 participants