Questions about Container Infrastructure Recommendation API Response

[yunkon-kim]

@hanizang77

1. What is the minimum version of Tumblebug required to replace tbmodel.TbMciDynamicReq with tbmodel.TbK8sClusterDynamicReq?

cm-beetle/pkg/core/recommendation/recommendation.go

Lines 373 to 381 in 1898377

	func RecommendContainer(provider, region string, srcInfra inframodel.OnpremInfra) (RecommendedInfraInfo, error) {
	var emptyResp RecommendedInfraInfo
	var result RecommendedInfraInfo
	result.TargetInfra = tbmodel.TbMciDynamicReq{
	Description: "Recommended Kubernetes node configuration by CM-Beetle",
	Name: "recommended-k8s-cluster",
	Vm: []tbmodel.TbVmDynamicReq{}, // a field to contain Kubernetes node information
	}

2. Is there anything else that should be considered to replace tbmodel.TbMciDynamicReq?

[hanizang77]

1️⃣ Minimum Required Version

To replace TbMciDynamicReq with TbK8sClusterDynamicReq, and to ensure the related APIs (/tumblebug/k8sClusterRecommendNode, /tumblebug/k8sClusterDynamicCheckRequest) are available, the minimum required version of Tumblebug is v0.10.6.

This is the first tagged release that includes commit 6a17833a,
which introduced support for TbK8sClusterDynamicReq and the necessary dynamic provisioning APIs.

---

2️⃣ Field Mapping and Gaps

Thanks for sharing the struct definitions — this confirms that while the current RecommendContainer() function covers part of the required fields in TbK8sClusterDynamicReq, it does not yet satisfy all required inputs.

✅ The following fields can already be filled:

• commonSpec: from /k8sClusterRecommendNode
• commonImage: from /k8sClusterDynamicCheckRequest
• description: (e.g., "Recommended K8s node")

❌ The following fields still need to be derived or manually filled:

• name, namespace, nodeGroupName: currently not generated
• version: not retrieved; /availableK8sVersion may help
• desiredNodeSize, minNodeSize, maxNodeSize: could be inferred from len(srcInfra.Servers)
• rootDiskType, rootDiskSize: default values can be set
• connectionName: may be selected from the ConnectionConfigCandidates in CheckK8sClusterDynamicReqInfo
• label, tags: not used yet

In summary, replacing TbMciDynamicReq with TbK8sClusterDynamicReq is feasible,
but requires supplemental logic to populate additional metadata and control fields.

Would it help if I proposed a refactored return structure for RecommendContainer() aligned with TbK8sClusterDynamicReq?

[yunkon-kim]

@hanizang77 Thank you!

We can get a recommended Kubernetes infrastructure by RecommendContainer(). It will be an input for the /ns/{nsId}/k8sClusterDynamic API in Tumblebug.

The API requires the user to fill in required fields and uses default values ​​for the rest.

Thus, I think prioritizing the required fields would be good for us.

[powerkimhub]

• This function's purpose and name might need review.

cm-beetle/pkg/core/recommendation/recommendation.go

Line 373 in 1898377

func RecommendContainer(provider, region string, srcInfra inframodel.OnpremInfra) (RecommendedInfraInfo, error) {

• e.g. RecommendContainerInfra(), RecommendInfraInfo(), RecommendContainerInfraInfo(), RecommendContainerClusterNodeSpecs(), ...