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.

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

Deprecate & remove "clusterctl alpha topology plan" #10138

Open
sbueringer opened this issue Feb 12, 2024 · 3 comments
Open

Deprecate & remove "clusterctl alpha topology plan" #10138

sbueringer opened this issue Feb 12, 2024 · 3 comments
Labels
area/clusterctl Issues or PRs related to clusterctl kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. 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

@sbueringer
Copy link
Member

sbueringer commented Feb 12, 2024

We recently closed a few issues - which would have been necessary to get "clusterctl alpha topology plan" into a good state - because there was no interest to implement them:

After a discussion in the Cluster API office hours from 24h January we decided to remove the command.

This issue tracks the removal of the command.

For folks using the command to dryrun the clusterctl topology reconciliation the best known alternative is to setup a management cluster via kind and then run the reconciliation in that cluster (ideally in some way that no actual infrastructure is created, e.g. by using invalid credentials).

While this is more effort, it allows folks to use Runtime Extensions and also solves the other issues in #7245 and #7246.

@sbueringer sbueringer added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. area/clusterctl Issues or PRs related to clusterctl labels Feb 12, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Feb 12, 2024
@sbueringer sbueringer changed the title Remove "clusterctl alpha topology plan" Deprecate & remove "clusterctl alpha topology plan" Feb 12, 2024
@sbueringer
Copy link
Member Author

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 12, 2024
@fabriziopandini
Copy link
Member

fabriziopandini commented Feb 27, 2024

Deprecation done.
We can figure out removal or alternative paths, like e.g. descoping the command to generate desired state only; also we can move the execution of this command into a controller (eg. using a new crd) so we can use runtime extensions

@fabriziopandini
Copy link
Member

/priority important-longterm

@k8s-ci-robot k8s-ci-robot added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/clusterctl Issues or PRs related to clusterctl kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. 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
Development

No branches or pull requests

3 participants