Support anyOf/oneOf/allOf/not schema constraints for ClusterClass variables #10636
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
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 ClusterClass developer, I would like to make use of anyOf/oneOf/allOf/not schema constraints for ClusterClass variables in order to describe more complex variable schema definitions.
Detailed Description
In order to support objects, lists and maps that can support only certain combinations of properties, it would be very useful to support anyOf/oneOf/allOf/not schema constraints. This enables describing which property combinations are valid, which are mutually exclusive, etc.
Anything else you would like to add?
No response
Label(s) to be applied
/kind feature
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.
The text was updated successfully, but these errors were encountered: