Make creation of imported clusters use v3/management cluster instead of v1/provisioning #13151
Labels
area/clusterprovisioningv2
kind/enhancement
QA/dev-automation
Issues that engineers have written automation around so QA doesn't have look at this
Milestone
Is your feature request related to a problem? Please describe.
There is an inconsistency between POST operations for imported cluster. We want to make it more consistent and avoid adding non-provisioning fields or duplicating fields from the v3 cluster to the v1 cluster.
Describe the solution you'd like
We want to switch to using v3/management cluster for both POST operations (creation and edit, currently it is only used for edit).
The text was updated successfully, but these errors were encountered: