v0.33.0

This release brings exciting new features and essential bug fixes.

🚀 Features:

1. API Bump: We've upgraded the APIs to version v1beta1.
2. Template Functions: enhance your templates with powerful new functions:: toToml, fromToml, toYaml, fromYaml, etc. Explore the full list of functions in PR #586
3. Fine-tune your add-ons and applications with post-rendering patches: make adjustments to generated manifests before they reach managed clusters. This allows for granular control over your deployments. PR #607
4. Dynamic Referenced Resources: Define referenced resources dynamically within templates. Use cluster namespace, name, and type for flexible deployments. See more in PR #610;
5. Selective Drift Detection: In ContinuosWithDriftDetection mode, you can now exclude specific resources from configuration drift monitoring. This provides more granular control over drift detection. Details in PR 612
6. User data can be stored in SveltosCluster: those data can be used among the other things with templating PR 315

🐛 Bug Fixes

1. Stale Resource Identification: Improved logic ensures accurate identification and handling of outdated resources.PR 582
2. CRD Removal Handling: Drift detection now correctly reacts to the removal of Custom Resource Definitions (CRDs). PR 206

v0.32.0

🐛 Bug Fixes

• Set ttlSecondsAfterFinished on Job that register management cluster. If Job is left after registration succeeds, helm upgrade for projectsveltos fails
• Correctly set version for addon-controller and classifier so on upgrade drift-detection-manager and sveltos-agent are upgraded

v0.31.0

🐛 Bug Fixes

• Fix bug: this caused resources to not be properly cleaned up when a ClusterProfile/Profile was deleted or stopped matching a cluster
• Fix but: this caused Sveltos to fail parsing certain YAML stored in secret/configMap or kustomizationRef
• Fix bug: this caused Sveltos to fail deploying content of a KustomizationRef.
• Increased memory limits for sveltos-agent and drift-detection-manager

v0.30.0

🚀 Features:

• Tiers: The concept of tier is introduced to manage deployment priority for resources targeted by multiple configurations. More info on this PR

🐛 Bug Fixes

• Correctly handle ConfigMap/Secret whose data section contains resources that in turns contains "---". Bug
• When profile contains multiple helm charts and deploying one fails, all installed charts are reported. Bug
• A (non default) separate image addon-controller is built that contains git binary. This will allow Kustomize files referencing other remote kustomize resources to be properly built. Bug

🌱 Others

1. Advanced clustrerAPI to v1.7.2
2. Advanced Helm SDK to v3.15.0
3. Advanced kind cluster

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)