Open chanwit opened 8 months ago
Hey @chanwit I suggest having the alpha and beta features behind feature flags. For beta you could enable those features by default but still allow cluster admins to disable them. For alpha, people should opt-it, thus making them aware they are using unstable features that could incur breaking changes. You can use the package we have in Flux for this, here is an example https://github.com/fluxcd/kustomize-controller/blob/main/internal/features/features.go
We have many features in the controller. Some of them are causing production issues. We need to list all of available features we're providing and grading them as
alpha
,beta
andga
.alpha
means the feature is experimental, and not ready for production yet.beta
means the feature is stable, it is ok to use on production with cautions.ga
general available means the feature is stable, confirmed to be working by many users, so it's ready for production use.Feature: auto reconciliation
ga
Feature: force unlocking
alpha
Feature: namespace multi-tenancy
beta
Sub tasks