Improve Cluster Validation webhooks for .spec.topology.version #10049
Labels
area/api
Issues or PRs related to the APIs
kind/feature
Categorizes issue or PR as related to a new feature.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
What would you like to be added (User Story)?
As a user I would like changes to the
Cluster.topology.version
field to be blocked when:KCP.spec.version != (current) Cluster.spec.topology.version
.spec.version != (current) Cluster.spec.topology.version
there are MachineSets with.spec.replicas > 0
with a.spec.version != (current) Cluster.spec.topology.version
to
As a user I would like to overwrite the version validation webhook to skip
.spec.topology.version
based validations (except semver) to fix screwed up clusters.Detailed Description
This is supposed to extend and improve the existing version validations.
For a better picture: the current implementation for version validations:
.spec.topology.version
cannot be decreased.spec.topology.version
cannot be increased by >= 2 minor versions.spec.topology.version
cannot be increased by >= 2 minor versionsProposed changes (same as User stories above, but maybe more detailed):
.spec.version != current .spec.topology.version
.spec.version != current .spec.topology.version
There are any MachineSets with.spec.replicas > 0
with a.spec.version != current .spec.topology.version
unsafe.topology.cluster.x-k8s.io/disable-version-validation
to skip all.spec.topology.version
validations (except semver)Anything else you would like to add?
Related issue which would propably be solved:
Label(s) to be applied
/kind feature
/area api
The text was updated successfully, but these errors were encountered: