Versioning of MCM with new MachineAPIs

[prashanth26]

The machine-controller-manager soon is expected to implement a newer version of MachineAPI on the closure of this issue. However, with this we need a mechanism to explicitly indicate that there is a change in API versioning and MCM support. The question here is how this can be handled? There are two aspects to consider here,

1. MachineAPI versioning

• Stick to v1alpha1? or move to something like v1alpha2/v1beta1?

2. Machine-controller-manager release semantic versioning

• Continue with 0.X.Y versioning with a new minor release or move to 1.0.0. release for the new APIs?

CC: @amshuman-kr @PadmaB @hardikdr @swapnilgm

[prashanth26]

The following steps are required to make OOT available to external parties to make use of the feature

• Create CI script for machine-spec
• New Release for machine-spec
• Create CI script for MCM-AWS
• New Release for MCM-AWS
• Rebase MCM/cmi-client with master. Wait for taints support in master before doing this?
• Refactor unit tests for MCM
• Refactor integration tests for MCM
• Refactor CI script for new MCM
• New MCM release - Issue #230.
• SampleProviders repo had to be updated with test overview Issue AWS#8

Points to consider for the future

• Make use of gRPC metadata to avoid unnecessary calls.

[prashanth26]

Closing this issue in favor of - https://github.com/gardener/machine-controller-manager/releases/tag/v0.30.0. We stuck to v1alpha1 and release version to continue with minor release.