Adding proxy configuration to the guest cluster wouldnt rollout the nodes

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

• New control plane and worker nodes are deployed and powered on, but they are not registered as cluster members, and no pods start on them.
• Cluster events, visible when describing the cluster from the Supervisor context, show errors similar to:
  Internal error occurred: failed calling webhook "<validating-webhook>": failed to call webhook:
Post "https://<webhook-application>:443/validate/fail?timeout=30s": dial tcp ###.###.###.###:443: connect: connection refused
• Multiple, or all, associated application pods are stuck in a CrashLoopBackOff state.

Environment

VKr 1.32 and Greater

Cause

The update is currently blocked because the specific webhooks necessary for maintaining the cluster's integrity, which are part of the hosted application, were not satisfied during the updating process.

Resolution

To resolve the application and webhook issues, please contact your application support team for review