(feat) Per-Cluster Patches for sveltos-agent and sveltos-applier #421
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This update introduces the ability to apply unique configuration patches to the sveltos-agent and sveltos-applier resources for individual managed clusters. Sveltos deploys a sveltos agent (and a sveltos-applier when in pull mode) in every managed cluster While patching the default configuration was supported, the same patch was applied uniformly across all managed clusters. This enhancement addresses scenarios requiring cluster-specific configuration overrides. For example, a cluster located in a specific geographic region might need to pull the image from a different private container registry than a cluster in another region. Managed clusters can now define the `sveltosagent.projectsveltos.io/config-override-ref` and `sveltosapplier.projectsveltos.io/config-override-ref` annotations to reference a ConfigMap containing the desired patches. The ConfigMap reference supports the following formats: 1. `<namespace>/<name>`: Explicitly specifies the namespace and name of the ConfigMap. 2. `<name> (or /<name>)`: Assumes the ConfigMap is in the same namespace as the annotated Cluster instance. As with global override, the configuration data within the ConfigMap must be a patch of one of the following types: 1. Strategic Merge Patch 2. JSON Patch (RFC6902)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This update introduces the ability to apply unique configuration patches to the sveltos-agent and sveltos-applier resources for individual managed clusters.
Sveltos deploys a sveltos agent (and a sveltos-applier when in pull mode) in every managed cluster While patching the default configuration was supported, the same patch was applied uniformly across all managed clusters.
This enhancement addresses scenarios requiring cluster-specific configuration overrides. For example, a cluster located in a specific geographic region might need to pull the image from a different private container registry than a cluster in another region.
Managed clusters can now define the
sveltosagent.projectsveltos.io/config-override-refandsveltosapplier.projectsveltos.io/config-override-refannotations to reference a ConfigMap containing the desired patches.The ConfigMap reference supports the following formats:
<namespace>/<name>: Explicitly specifies the namespace and name of the ConfigMap.<name> (or /<name>): Assumes the ConfigMap is in the same namespace as the annotated Cluster instance.As with global override, the configuration data within the ConfigMap must be a patch of one of the following types: