On 24/2/24 06:20, Satish Patel wrote:
Folks,
I am silently reading this thread. Recently we deployed magnum with "magnum-cluster-api" driver in production and I am very happy with all the functionality. I wasn't aware of the "magnum-capi-helm" driver and if you are saying it will be native driver then what should we expect in future? Is it going to break our deployment with future upgrades or we will have a choice to pick either one?
Just looking for clarification and future expectations.
The contributed 'capi-helm' is A driver (emphasis not THE driver). You can install many other drivers if you wish. The work so far[1] (in this cycle) is to make sure multiple drivers work together without breaking, so production deployments using out-of-tree drivers (that magnum core team doesn't know about) don't get broken when we introduce new drivers. The breakage has nothing to do with CAPI, in fact if someone introduces a heat driver for Ubuntu OS it would have clashed with VEXXHOST's magnum-cluster-api driver too[2]. Depending on how many drivers you want to install, you may need to explicitly 'hint' what driver should be used, but the way of a glance tag. This also allows you to do cool things like have multiple drivers running if you want to migrate off one driver to another. Whether capi-helm deserves to be in-tree or not is a separate conversation; I just want to assure you of the effort towards not breaking your deployment. Regards, Jake [1] https://review.opendev.org/c/openstack/magnum/+/907297 [2] https://github.com/vexxhost/magnum-cluster-api/blob/v0.13.4/magnum_cluster_a...