The maxsurge-0 scenario is broken at least for kubeadm. This scenario is used on the nightly scheduled pipeline : https://gitlab.com/sylva-projects/sylva-core/-/wikis/Scheduled-pipelines-report#capo-kadm-nightly-capo-fiphamaxsurge-0-ubuntu Current behavior : The cluster helm release is in error due to : ``` 'Could not determine release state: unable to determine cluster state: MachineDeployment/sylva-system/mgmt-2500960308-kubeadm-capo-md0 dry-run failed: failed to create typed patch object (sylva-system/mgmt-2500960308-kubeadm-capo-md0; cluster.x-k8s.io/v1beta2, Kind=MachineDeployment): .spec.strategy: field not declared in schema' ``` I don't know if it's an issue only with the values of our CI (https://gitlab.com/sylva-projects/sylva-elements/ci-tooling/ci-deployment-values/-/blob/main/common/maxsurge-0.yml?ref_type=heads) or if it's related to sylva-capi-cluster. \ (i 'll update the issue soon and the title)