Configure NCP subnets to use single zone for cluster creation#2137
Merged
cb-github-robot merged 2 commits intocloud-barista:mainfrom Sep 4, 2025
Merged
Configure NCP subnets to use single zone for cluster creation#2137cb-github-robot merged 2 commits intocloud-barista:mainfrom
cb-github-robot merged 2 commits intocloud-barista:mainfrom
Conversation
- Modify NCP subnet creation logic to use zones[0] instead of zones[1] to meet single-AZ requirement for NCP K8s clusters (ref: cloud-barista#2136)
- Add NCP-specific settings including versions, node group rules, and disk configurations
Member
|
/approve |
Member
|
/lgtm |
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
4 participants
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.
Problem
NCP K8s cluster creation requires all subnets (including LB subnets) to be within the same availability zone, unlike other CSPs that support multi-AZ deployments. Current logic was assigning subnets to different zones, causing K8s cluster creation failures.
Solution
Testing
Testing Details
API Used:
k8sClusterDynamicRequest Body:
{ "imageId": "default", "specId": "ncp+kr+ci2-g3", "connectionName": "ncp-kr", "name": "k8scluster02", "nodeGroupName": "k8sng02" }Fixes #2136