kubernetes-sigs
Consider blocking ClusterClass rebase between CCs with and without a CP machineInfrastructure
ClusterClassesAreCompatible currently only checks compatitbility of both current & desired MachineInfrastructures are defined
xref: https://github.com/kubernetes-sigs/cluster-api/pull/12545#discussion_r2244922062
cc @fabriziopandini
Makes sense, +1 from me enforcing that rebase can happen only after the topology is created
enforcing that rebase can happen only after the topology is created
What does this have to do with this issue? :)
Before topology is created, in theory we don't care if we transition from something with or without CP infrastructure. (but it is also perfectly fine to ignore this edge case, creating a topology is usually quick) /help
@fabriziopandini: This request has been marked as needing help from a contributor.
Guidelines
Please ensure that the issue body includes answers to the following questions:
- Why are we solving this issue?
- To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
- How can the assignee reach out to you for help?
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.
In response to this:
Before topology is created, in theory we don't care if we transition from something with or without CP infrastructure. (but it is also perfectly fine to ignore this edge case, creating a topology is usually quick) /help
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
