v0.29.1

🚀 Features:

• KustomizationRef.Path and PolicyRef.Path can be expressed as templates and instantiate at run-time using Cluster metadata info PR

v0.29.0

🚀 Features:

1. Helm charts values can be collected from referenced ConfigMap/Secret (PR)
   2.Define your Kustomize builds as templates. Sveltos can then instantiate them using key-value pairs provided directly in your ClusterProfile/Profile or referenced from Secrets/ConfigMaps. These key-value pairs themselves can also be templates, allowing for even more dynamic configurations based on resources in your management cluster (PR)

🐛 Bug Fixes

1. Run helm install with replace flag set (PR)

🌱 Others

1. Bump Kubernetes to v1.30.0, controller-runtime to v1.18.1 and clusterAPI to v1.7.1

v0.28.0

🚀 Features:

• management cluster is automatically registered to be managed by Sveltos;
• sveltosctl register command has been expanded to specify labels SveltosCluster should have;
• sveltosctl generate kubeconfig has been introduced. Running this command while pointing to the managed cluster, will generate and output a Kubeconfig that can be later on consumed by sveltosctl register cluster
• sveltosctl register command accepts a new flag fleet-cluster-context that can be set to the context pointing to the managed cluster. So this command can be run with default context pointing to the management cluster and it will automatically generate a kubeconfig and register the cluster in one shot.

🐛Bug fixed:

• add-on controller will correctly redeploy and helm chart when its values are modified (read more about bug here)

v0.27.0

🚀 Features:

• EventTrigger can reference ClusterSet
• images are built for amd64 and arm64

This release contains a non backward compatible change. ClusterProfile/Profile when referencing ClusterSet/Set respectively, only need to specify the name.

v0.26.0

🚀 Features:

• Introduce ClusterSet/Set: Those CRDs can be used to select clusters (using as usual clusterSelector) and have another field specifying how many of the matching clusters should be selected. For instance 2 clusters might match a Set but only one will be selected. This is useful when you want to implement active/passive failover: Create a ClusterSet/Set with maxReplicas: 1 and have it match two clusters in the clusterSelector. This ensures only one cluster is active at a time. If the active cluster goes down, the backup cluster will be automatically selected for deployments.
  ClusterProfile can reference a ClusterSet (and a Profile can reference a Set). The add-ons defined in the ClusterProfile will be deployed only to the currently selected clusters within the referenced ClusterSet. This enables dynamic deployment management based on the available and healthy clusters in the set.

v0.25.0

🚀 Features:

• MS Team notification support

🐛 Bug Fixes:

• Fix for inconsistent template naming (inconsistent between code and documentation)
• Fix for the extra labels/annotations metadata

🌱 Others:

• Remove rbac proxy container (metric will be fetched directly from the main container)
• Optimisation to avoid keep trying to reconciler clusters when those become not ready

v0.24.0

🚀 Features:

• ClusterProfile/Profile allows specifying extra metadata (labels and annotations) which will be added to all resources deployed by Sveltos (YAML/JSON, Helm charts, Kustomize)

🐛 Bug Fixes:

• Filtering by cluster name in sveltosctl show addons

v0.23.0

🚀 Features:

• Allows Sveltos to get YAMLs/JSONs from flux sources

v0.22.0

🚀 Features:

• Allows to configure, per helm release, following helm options: skipCRDs, Wait, WaitForJobs, Atomic, DependencyUpdate, CreateNamespace;
• Health rules can be defined looking at objects of different GVKs all together. This allows for more complex health evaluations when Kubernetes resources need to be looked at together;
• deprecated add-on compliance validations.

🐛 Bug Fixes:

• Support for OCI registry;
• Avoid un-necessary helm upgrade (installed version vs expected version comparison fixed).

v0.21.1

🐛 Bug Fixes

• addon-controller not reacting to new cluster matching an existing profile bug
• addon-controller not cleaning up ClusterConfiguration for a deleted cluster which used to match a Profile bug
• resource deployed in drift-detection mode has spurious redeployment due to an issue detecting false configuration drift bug
• addon-controller logs reported an issue collecting ResourceSummary and ReloaderReport. That was a non issue as error was happening when ResourceSummary or the ReloaderSummary CRD were not deployed in a cluster bug