Skip to main content

Prism Central CMSP Deployment Failed Due to Kubernetes Network Overlap

  • Nov 3, 2026 8:10 AM UTC
  • 0 replies
  • 0 views

Muhammad_Magdy
Forum|alt.badge.img

While enabling the Microservices Infrastructure (CMSP) on Nutanix Prism Central, the deployment failed during the post-deployment prechecks with an error indicating that Prism Central was not compatible to enable Microservices Infrastructure.

๐Ÿ’ก ๐—ฅ๐—ผ๐—ผ๐˜ ๐—–๐—ฎ๐˜‚๐˜€๐—ฒ ๐—”๐—ป๐—ฎ๐—น๐˜†๐˜€๐—ถ๐˜€:
- When CMSP is enabled, Prism Central deploys an internal Kubernetes-based platform to host Nutanix microservices.
- For CMSP deployment on Prism Central, the CMSP internal services use the following default networks:
ย  --> ๐Ÿฃ๐Ÿซ๐Ÿค.๐Ÿฃ๐Ÿจ๐Ÿช.๐Ÿง.๐Ÿข/๐Ÿค๐Ÿฆ - ๐˜’๐˜ถ๐˜ฃ๐˜ฆ๐˜ณ๐˜ฏ๐˜ฆ๐˜ต๐˜ฆ๐˜ด ๐˜ช๐˜ฏ๐˜ง๐˜ณ๐˜ข๐˜ด๐˜ต๐˜ณ๐˜ถ๐˜ค๐˜ต๐˜ถ๐˜ณ๐˜ฆ ๐˜ฏ๐˜ฆ๐˜ต๐˜ธ๐˜ฐ๐˜ณ๐˜ฌ
ย  --> ๐Ÿฃ๐Ÿข.๐Ÿฃ๐Ÿข๐Ÿข.๐Ÿข.๐Ÿข/๐Ÿฃ๐Ÿจย - ๐˜’๐˜ถ๐˜ฃ๐˜ฆ๐˜ณ๐˜ฏ๐˜ฆ๐˜ต๐˜ฆ๐˜ด ๐˜ฑ๐˜ฐ๐˜ฅ ๐˜ฏ๐˜ฆ๐˜ต๐˜ธ๐˜ฐ๐˜ณ๐˜ฌ
ย  --> ๐Ÿฃ๐Ÿข.๐Ÿค๐Ÿข๐Ÿข.๐Ÿฅ๐Ÿค.๐Ÿข/๐Ÿค๐Ÿฆ - ๐˜’๐˜ถ๐˜ฃ๐˜ฆ๐˜ณ๐˜ฏ๐˜ฆ๐˜ต๐˜ฆ๐˜ด ๐˜ด๐˜ฆ๐˜ณ๐˜ท๐˜ช๐˜ค๐˜ฆ๐˜ด ๐˜ฏ๐˜ฆ๐˜ต๐˜ธ๐˜ฐ๐˜ณ๐˜ฌ
- The upstream network environment cannot overlap with these networks.ย 
- Since Kubernetes cannot differentiate between internal container traffic and the production management network, the CMSP prechecks intentionally block the deployment to prevent routing conflicts.

๐Ÿ”ง ๐—ฆ๐—ผ๐—น๐˜‚๐˜๐—ถ๐—ผ๐—ป:
- If the environment requires using these subnet ranges in the upstream network, you must change the CMSP internal network ranges prior to deploying Prism Central.
- Since the deployment had already failed, the first step was cleaning the incomplete CMSP deployment then configure the custom Pod and Service CIDRs
==
1๏ธโƒฃ SSH PCVM & Clean up the failed deployment:
๐˜ฑ๐˜บ๐˜ต๐˜ฉ๐˜ฐ๐˜ฏ /๐˜ฉ๐˜ฐ๐˜ฎ๐˜ฆ/๐˜ฅ๐˜ฐ๐˜ค๐˜ฌ๐˜ฆ๐˜ณ/๐˜ฎ๐˜ด๐˜ฑ_๐˜ค๐˜ฐ๐˜ฏ๐˜ต๐˜ณ๐˜ฐ๐˜ญ๐˜ญ๐˜ฆ๐˜ณ/๐˜ฃ๐˜ฐ๐˜ฐ๐˜ต๐˜ด๐˜ต๐˜ณ๐˜ข๐˜ฑ/๐˜ฎ๐˜ด๐˜ฑ_๐˜ต๐˜ฐ๐˜ฐ๐˜ญ๐˜ด/๐˜ค๐˜ฎ๐˜ด๐˜ฑ-๐˜ด๐˜ค๐˜ณ๐˜ช๐˜ฑ๐˜ต๐˜ด/๐˜ค๐˜ฎ๐˜ด๐˜ฑ-๐˜ค๐˜ญ๐˜ฆ๐˜ข๐˜ฏ๐˜ถ๐˜ฑ.๐˜ฑ๐˜บ --๐˜ง๐˜ฐ๐˜ณ๐˜ค๐˜ฆ
|
2๏ธโƒฃ Configure new CMSP networks:
* Edit the Genesis gflags:
~/๐˜ด๐˜ฆ๐˜ณ๐˜ท๐˜ช๐˜ค๐˜ฆ๐˜ข๐˜ฃ๐˜ช๐˜ญ๐˜ช๐˜ต๐˜บ/๐˜ฃ๐˜ช๐˜ฏ/๐˜ฆ๐˜ฅ๐˜ช๐˜ต-๐˜ข๐˜ฐ๐˜ด-๐˜จ๐˜ง๐˜ญ๐˜ข๐˜จ๐˜ด --๐˜ด๐˜ฆ๐˜ณ๐˜ท๐˜ช๐˜ค๐˜ฆ=๐˜จ๐˜ฆ๐˜ฏ๐˜ฆ๐˜ด๐˜ช๐˜ด
* Update the default networks to unused subnets, for example:
--๐˜ค๐˜ฎ๐˜ด๐˜ฑ_๐˜ฑ๐˜ฐ๐˜ฅ_๐˜ฏ๐˜ฆ๐˜ต๐˜ธ๐˜ฐ๐˜ณ๐˜ฌ=๐Ÿฃ๐Ÿฉ๐Ÿค.๐Ÿฃ๐Ÿจ.๐Ÿข.๐Ÿข/๐Ÿฃ๐Ÿจ
--๐˜ค๐˜ฎ๐˜ด๐˜ฑ_๐˜ด๐˜ฆ๐˜ณ๐˜ท๐˜ช๐˜ค๐˜ฆ_๐˜ช๐˜ฑ_๐˜ฏ๐˜ฆ๐˜ต๐˜ธ๐˜ฐ๐˜ณ๐˜ฌ=๐Ÿฃ๐Ÿฉ๐Ÿค.๐Ÿฃ๐Ÿฉ.๐Ÿฅ๐Ÿค.๐Ÿข/๐Ÿค๐Ÿฆ
|
3๏ธโƒฃ Restart Genesis:
๐˜จ๐˜ฆ๐˜ฏ๐˜ฆ๐˜ด๐˜ช๐˜ด ๐˜ณ๐˜ฆ๐˜ด๐˜ต๐˜ข๐˜ณ๐˜ต
|
4๏ธโƒฃ Re-deploy CMSP again:
๐˜ค๐˜ฅ /๐˜ฉ๐˜ฐ๐˜ฎ๐˜ฆ/๐˜ฅ๐˜ฐ๐˜ค๐˜ฌ๐˜ฆ๐˜ณ/๐˜ฎ๐˜ด๐˜ฑ_๐˜ค๐˜ฐ๐˜ฏ๐˜ต๐˜ณ๐˜ฐ๐˜ญ๐˜ญ๐˜ฆ๐˜ณ/๐˜ฃ๐˜ฐ๐˜ฐ๐˜ต๐˜ด๐˜ต๐˜ณ๐˜ข๐˜ฑ/๐˜ฎ๐˜ด๐˜ฑ_๐˜ต๐˜ฐ๐˜ฐ๐˜ญ๐˜ด/๐˜ค๐˜ฎ๐˜ด๐˜ฑ-๐˜ด๐˜ค๐˜ณ๐˜ช๐˜ฑ๐˜ต๐˜ด/
Then
๐˜ฑ๐˜บ๐˜ต๐˜ฉ๐˜ฐ๐˜ฏ ๐˜ค๐˜ฎ๐˜ด๐˜ฑ-๐˜ฆ๐˜ฏ๐˜ข๐˜ฃ๐˜ญ๐˜ฆ.๐˜ฑ๐˜บ
|
5๏ธโƒฃ Monitor the deployment progress:
* Check the infrastructure tasks
๐˜ฆ๐˜ค๐˜ญ๐˜ช ๐˜ต๐˜ข๐˜ด๐˜ฌ.๐˜ญ๐˜ช๐˜ด๐˜ต ๐˜ค๐˜ฐ๐˜ฎ๐˜ฑ๐˜ฐ๐˜ฏ๐˜ฆ๐˜ฏ๐˜ต_๐˜ญ๐˜ช๐˜ด๐˜ต=๐˜ช๐˜ฏ๐˜ง๐˜ณ๐˜ข
Or
* Monitor the CMSP deployment pipeline
๐˜ฎ๐˜ด๐˜ฑ๐˜ค๐˜ต๐˜ญ ๐˜ต๐˜ข๐˜ด๐˜ฌ ๐˜ญ๐˜ช๐˜ด๐˜ต
ย 

ย