Feature: MachineSetPreflightChecks

[sbueringer]

• CAEPs: -
• Documentation: https://cluster-api.sigs.k8s.io/tasks/experimental-features/machineset-preflight-checks
• Feature gate state:
  • Alpha (disabled per default): v1.5
  • Beta (enabled per default): v1.9
  • Stable (feature GA): TBD
  • Feature gate removed 1 release later: TBD

[sbueringer]

I would like to move this feature to beta and enabled per default in CAPI v1.9.

We've been using this feature in production since it's introduction (in CAPI v1.5).

@fabriziopandini @enxebre @vincepri @killianmuldoon @chrischdi Opinions?

[fabriziopandini]

+1 from me!

Might be, we need a flag to allow folks disabling preflight checks for an entire setup before graduation.

[sbueringer]

(I might be misunderstanding what you are suggesting)

I'm only proposing to change the feature gate to: Beta & Default: true at this point (

cluster-api/feature/feature.go

Line 79 in 128914b

MachineSetPreflightChecks: {Default: false, PreRelease: featuregate.Alpha},

)

This then still allows folks to disable it

[fabriziopandini]

Sorry for not providing enough details.

While there is a the feature flag, it can be used to disable preflight checks for an entire setup, that's correct.
However, after graduation, when the feature flag goes away, there won't be anymore any option to disable preflight checks for an entire setup.

This is why I think that we should consider adding a flag at controller level that allows to do this (we can eventually also build this flag in a way that you can disable specific checks for an entire setup, but TBD)

But we can also consider this after feedbacks when the feature flag is enabled by default

[chrischdi]

/assign

for the beta promotion for v1.9