Improve VNet CIDR management for GCP/IBM#2364
Merged
cb-github-robot merged 1 commit intocloud-barista:mainfrom Mar 12, 2026
Merged
Improve VNet CIDR management for GCP/IBM#2364cb-github-robot merged 1 commit intocloud-barista:mainfrom
cb-github-robot merged 1 commit intocloud-barista:mainfrom
Conversation
* Set user-provided CIDR for GCP and IBM to handle cases where the CSP doesn't support it * Fix missing ConnectionConfig on Subnet objects when creating vNet and subnets together
Member
|
/hold |
Member
|
Hi @yunkon-kim But, we need to complete test with Spider v0.12.8 since it is our current base is https://github.com/cloud-barista/cb-tumblebug/blob/main/docker-compose.yaml#L166 Please share the testing result of this PR based on the CB-TB latest commit (Spider v0.12.8) |
Member
|
/hold cancel |
Member
|
@yunkon-kim I guess your previous failure was based on missed configuration in the upstream while updating cb-spider version from v0.12.7 to v0.12.8 (this version includes several configuration changes. also, I heard there is a mistake within cb-spider)
I think the current cb-tb latest commit would be fine. :) |
Member
|
/approve |
This file contains hidden or 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
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.

This PR improves VNet CIDR management for GCP/IBM.
This will stabilize multi-cloud resource provisioning for GCP and IBM and resolve VNet creation hangs caused by missing CSP metadata.
Tumblebug will intentionally manage the user-provided vNet CIDR block as metadata, although CSPs (e.g., GCP, IBM) do not natively support vNet (VPC) CIDR blocks.
Note - From a management perspective, this helps users (e.g., admin, network operator) easily manage network addresses and prevent errors during resource creation on different cloud platforms.
Improvements
Test environment
v0.12.7-> v0.12.8Note: potential compatibility issues identified with v0.12.8; further verification required.Before and after
GCP
vNetInfo.cidrBlock: "GCP VPC does not support IPv4_CIDR"vNetInfo.cidrBlock: "10.0.0.0/16"IBM
vNetInfo.cidrBlock: "IBM VPC does not support IPv4_CIDR"vNetInfo.cidrBlock: "10.0.0.0/16"Note - I'd like to skip to show the ConnectionConfig info of subnets ;)
References