502 Error After Migrating from TMC SaaS to TMC SM
Article ID: 405572
Updated On:
Products
VMware Tanzu Mission Control
Issue/Introduction
In the process of migrating TMC SaaS to SM, after installing TMC SM, clicking on Cluster > Configure > TKG Service > Default CNI and Tanzu Mission Control, vCenter UI returns "502 Bad Gateway".
Cause
This can happen when the new TMC SM URL is different from the previous SaaS URL.
Resolution
Update the TMC URL and restart the tkg-plugin pods.
Feedback
Yes
No
Powered by
