Open chrischdi opened 1 month ago
Yup also
I think this is a great idea, and we should do this for all fields now & going forward
/triage accepted /help
we can evaluate case by case on follow up PRs
@fabriziopandini: This request has been marked as needing help from a contributor.
Please ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help
command.
Yup also
- Consider deprecation of revision management in MachineDeployments #10479
- Deprecated definitionFrom in cluster variables #10666
- ✨ Add metadata for top-level and nested variables & deprecate previous metadata field #10778
- experimentalRetryJoin
I think this is a great idea, and we should do this for all fields now & going forward
moved these up to the list
What would you like to be added (User Story)?
As a user I would like to get a warning when I make use of deprecated fields.
Detailed Description
We already have some deprecated fields:
Cluster.spec.topology.rolloutAfter
DockerMachine.spec.bootstrapped
ClusterClass.spec.Variables[].Metadata
?and considering e.g.:
10708
we may introduce more in future.
For providing a user the information that it makes use of a deprecated field, we could use warnings in validation to bubble that information up.
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.