scaletest: Align kops scalability configuration with kube-up for kubelet maxPods#18083
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/test pull-kops-gce-master-scale-performance-100 |
Signed-off-by: ronaldngounou <ronald.ngounou@yahoo.com>
fa88751 to
8186f45
Compare
|
Rebased |
|
@ronaldngounou: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
|
This change might have unintended consequences for AWS with VPC CNI, due to the number of pre-allocated IPs. |
Align kops scalability configuration with kube-up by setting
spec.kubelet.maxPods=110to match the kubernetes default values.Contributes to #18070