Skip to content

RFE: Runtime Hooks for Add-on Management #6374

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

Closed
killianmuldoon opened this issue Apr 4, 2022 · 1 comment · Fixed by #6418
Closed

RFE: Runtime Hooks for Add-on Management #6374

killianmuldoon opened this issue Apr 4, 2022 · 1 comment · Fixed by #6418
Labels
area/runtime-sdk Issues or PRs related to Runtime SDK kind/feature Categorizes issue or PR as related to a new feature. kind/proposal Issues or PRs related to proposals.
Milestone

Comments

@killianmuldoon
Copy link
Contributor

Cluster API is currently unable to enable comprehensive add-on management because of the inability to interact with the lifecycle of a Cluster. This issue proposes a number of RuntimeHooks, based on the Runtime SDK, which will enable external management of add-ons based on transitions in the Cluster lifecycle.

The full proposal is available at this link.

This proposal is related to recent conversations about add-ons and leverages features developed as part of the Cluster Topology proposal , and will be based on implementation of the Runtime SDK #6181.

/kind feature
/area runtime-sdk
/kind proposal

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. area/runtime-sdk Issues or PRs related to Runtime SDK kind/proposal Issues or PRs related to proposals. labels Apr 4, 2022
@fabriziopandini
Copy link
Member

Yay!
/milestone v1.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/runtime-sdk Issues or PRs related to Runtime SDK kind/feature Categorizes issue or PR as related to a new feature. kind/proposal Issues or PRs related to proposals.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants