Support settings for RuntimeExtensions #7432
Labels
area/runtime-sdk
Issues or PRs related to Runtime SDK
kind/feature
Categorizes issue or PR as related to a new feature.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
User Story
As a RuntimeExtensions author, I would like to offer settings allowing cluster administrators to tune my RuntimeExtensions behavior when installed on a management cluster
As a RuntimeExtensions author, I would like to offer settings allowing cluster class authors to tune my RuntimeExtensions behavior when used in a ClusterClass
Detailed Description
RuntimeExtension is a powerful mechanism for extending Cluster API and we expect RuntimeExtensions to become more and more complex over time. This will lead RuntimeExtensions authors to expose settings allowing users to customize RuntimeExtensions behavior on different clusters or when used in different ClusterClass.
Eg. I have Runtime extension with a couple of lifecycle hooks, and on specific management clusters I want to disable some of them or simply tune the RequeAfter interval
Eg. I have Runtime extension with many external patches, and on specific ClusterClasses I want to disable some of them
RuntimeExtension extension can implement those use cases in many ways, exposing flags, checking for setting in a config map etc. etc. but all those approaches won't be integrated with Cluster API (so the users will be required to change RuntimeExtension deployment or to act on different objects).
With this issue we are proposing to introduce a setting fields both in
And in
/kind feature
/area runtime-sdk
The text was updated successfully, but these errors were encountered: