Introduce Reloader knob on ClusterProfile #289
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add-ons are deployed using Sveltos including Deployments, StatefulSets and DaemonSets. Such instances can mount ConfigMaps/Secrets as volume.
When Reloader knob is set to true, add-on controller will deploy, in the managed cluster, a Reloader instance. There is one Reloader instance per ClusterProfile, feature id pair. Feature ids are helm, kustomize and resources. Reloader instance contains all Deployment, StatefulSet and DaemonSet deployed in the managed cluster by sveltos because of the ClusterProfile, feature id pair.
Reloader instance will then be processed by sveltos-agent. Sveltos-agent will report back to management cluster, via ReloaderReport, when a ConfigMap or Secret mounted changes. So that sveltos can trigger a rolling upgrade.
Default value for Reloader knob is false.