-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Update default instance types for AWS #8282
Conversation
Hi @hakman. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cc @rifelpet |
@@ -1345,13 +1345,13 @@ func (c *awsCloudImplementation) DefaultInstanceType(cluster *kops.Cluster, ig * | |||
// Some regions do not (currently) support the m3 family; the c4 large is the cheapest non-burstable instance | |||
// (us-east-2, ca-central-1, eu-west-2, ap-northeast-2). | |||
// Also some accounts are no longer supporting m3 in us-east-1 zones | |||
candidates = []string{"m3.medium", "c4.large"} | |||
candidates = []string{"c5.large", "c4.large", "m3.medium"} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we want to consider a t3.large or t3.medium instead. We're more likely to be memory constrained.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
t3.* has CPU credits and may be throttled on master startup. Also, it has slower throttled network. Should be ok for a small clusters. If we see issues, I would go with m5.large.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's reasonable to tune the defaults for small clusters.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
t3.* default to unlimited, so won't be CPU throttled on startup. If the CPU utilization is at or below the baseline over the 24 hour period (or lifetime) then there won't be an overage charge. The only issues would seem to be the slower network or the possibility of higher cost if the CPU is used at a high sustained rate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I forgot about the part of Unlimited by default. In this case, it may be a good idea to set t3.medium as default for masters also. It should stay around 10% CPU usage, which is not charged extra. Network throttling is not so bad for a small cluster (baseline is 0,25 Gbit/s).
/ok-to-test |
aca2615
to
3c2dd46
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/assign @justinsb |
/lgtm |
I agree with these changes - but we should make a release note! I'm also not sure if we want to gate this on kubernetes version (or if we even can). It's an odd case because it's only for newly created clusters, but still if people are doing Let's just confirm the details in office hours today! |
3c2dd46
to
d83a3c6
Compare
d83a3c6
to
7a42cf4
Compare
/retest |
1 similar comment
/retest |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman, rifelpet 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 |
…pstream-release-1.17 Automated cherry pick of #8282: Set the default instance type to t3.medium for AWS
While doing the setup for some e2e I noticed that Kops has still defaults to some quite old types of instances. Any reason for not changing to c5, t3? These should be cheaper and faster.
PS: m3.medium is so old that it becomes irrelevant.