ci: fix gke network starvation #1654
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
With current defaults, the number of clusters that can be provisioned simultaneously in the same project is around 31. This commit changes default subnet range to /26, pod ip range to /21 and service ip range to /24. After these changes max clusters that can be provisioned will be more then 3500. Signed-off-by: Birol Bilgin <birol@cilium.io>
brlbil
force-pushed
the
pr/brlbil/ci-fix-gke-network-starvation
branch
from
599b8a3
to
355c1de
Compare
maintainer-s-little-helper
bot
added
the
ready-to-merge
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
cilium, andcilium-cliuse the same GCP project for provisioning GKE clusters.If the number of simultaneously provisioned clusters is high enough we get an error like below,
With current defaults, which are below, the number of clusters that can be provisioned simultaneously is around 31.
The current default network ranges are too big for our use cases, per cluster only 2 nodes are provisioned.
The max pods created is 29, and the max services created is 9
In accordance with network range requirements, the changes below have been made.
With these changes, the number of clusters that can be provisioned simultaneously is more than 3500.
Note: These changes have already been merged to
ciliumwith a recent PRSuccessful run links are below,
externalworkloads.yaml
gke.yaml
multicluster.yaml