Add n1-highmem-16 nodepool to k8s-infra-prow-build #1167
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To avoid delete/recreate of nodepool pool1
The intent is to cordon off the n1-highmem-8 nodepool, and shift jobs to this node pool. We're doing this to mitigate the fact that the cluster is configured to use an external IP for each new node, and we don't have enough IP quota to scale as large as PR traffic is requiring us to
k8s-ci-robot
added
cncf-cla: yes
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: spiffxp 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 |
k8s-ci-robot
added
the
approved
|
/lgtm |
k8s-ci-robot
added
the
lgtm
This was referenced Aug 21, 2020
spiffxp
added
the
area/prow
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The intent is to cordon off the n1-highmem-8 nodepool, and shift jobs to
this node pool.
We're doing this to mitigate the fact that the cluster is configured to use
an external IP for each new node, and we don't have enough IP quota to
scale as large as PR traffic is requiring us to
This is one of the suggested workarounds from #1132 (comment)