Failed to apply NodePool CR. Cluster: [CLUSTER_NAME], Operation: EditNodePool, Intent: ########-####-####-####-############, NodePool: [NODEPOOL_NAME], Details: HttpStatus: 422 : admission webhook "vtcanodepool.kb.io" denied the request: TcaNodePool.telco.vmware.com "[NODEPOOL_NAME]" is invalid: spec.network: Invalid value: "network": cannot be modified
network: devices: - dhcp4: true nameservers: - 192.168.0.100, 192.168.0.1012.2
Post-deployment, it is not supported to change the network configuration of a nodepool. In some scenarios, multiple nameservers may have been configured and in the K8s configuration they are stored as a comma-separated single line. Subsequent updates to the cluster may attempt to push the two nameservers each on their own line. While the data is not changed, K8s perceives this as a change and denies it.
Temporary disabling of the validating webhooks can allow for an override to be pushed to the configuration. The steps required provide a potential for irrecoverable issues and support should be engaged for guidance.