Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support anyOf/oneOf/allOf/not schema constraints for ClusterClass variables #10636

Open
jimmidyson opened this issue May 16, 2024 · 1 comment · May be fixed by #10637
Open

Support anyOf/oneOf/allOf/not schema constraints for ClusterClass variables #10636

jimmidyson opened this issue May 16, 2024 · 1 comment · May be fixed by #10637
Assignees
@jimmidyson
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.

Comments

@jimmidyson
Copy link
Member

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.
@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 16, 2024
@jimmidyson jimmidyson linked a pull request May 16, 2024 that will close this issue
Open
@fabriziopandini
Copy link
Member

We already added features to the initial implementation of cluster class variables, this one adds to list
/priority important-longterm

/triage accepted
given that there is already a PR for it

@k8s-ci-robot k8s-ci-robot added 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. and removed needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jimmidyson jimmidyson

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.
Projects
None yet
Milestone
No milestone
3 participants
@jimmidyson @fabriziopandini @k8s-ci-robot