Closed jichenjc closed 3 years ago
any thoughts on this? @christopherhein @Fei-Guo comments?
/assign
Yes. In current version, we don't consider vc upgrade through changing the cluster version name and we should add webhook to make this field immutable. We defer the upgrade story for cluster version based provisioning because we will design update worklflow based on CAPN in next step.
/close
Closing since this PR was implemented and merged.
@christopherhein: Closing this issue.
What steps did you take and what happened: [A clear and concise description on how to REPRODUCE the bug.]
What did you expect to happen:
success
expected: it should fail, we should consider only allow desired field to be updated and block others ..
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):/etc/os-release
):/kind bug [One or more /area label. See https://github.com/kubernetes-sigs/cluster-api-provider-nested/labels?q=area for the list of labels]