SDDC Manager Fails Edge Operations Fail Due to Out-of-Band Configuration Changes

Products

• VMware Cloud Foundation

Issue/Introduction

SDDC Manager does not support edge clusters created via SDDC-Manager that have been modified through out-of-band configuration changes after the initial edge cluster deployment. Any post-deployment changes made directly in NSX Manager or vCenter — outside of SDDC Manager workflows — will result in an unsupported state and may cause SDDC Manager operations on that edge cluster to fail or be blocked during validation.

Environment

VMware Cloud Foundation (VCF) 4.x, 5.x, and 9.x

Cause

SDDC Manager Edge Cluster workflows are prescriptive with rigid prerequisite validations at the time of deployment, expansion, and shrinkage. Changes made directly through NSX Manager, vCenter, or any other interface outside of SDDC Manager are not reflected in SDDC Manager's inventory, resulting in state mismatch, prerequisite breaking, and management failures. 

Once this divergence exists, SDDC Manager cannot reliably manage, validate, or remediate the edge cluster. Affected operations include but are not limited to:

• Edge cluster expansion or shrinkage
• Day-N operations that depend on the edge cluster

This is a global restriction that applies to all edge cluster configurations regardless of the nature of the out-of-band change.

Resolution

There is no supported in-place remediation path for an edge cluster modified out-of-band. To restore a supported state:

 

• Revert the OOB configuration change.
• Or, continue managing the OOB-modified edge cluster manually.

Do not modify edge cluster resources — including edge node VMs, resource pool, datastores, host placement, or NSX configuration — through any interface other than SDDC Manager after initial deployment.