v0.36.0

🚀 Features:

• Introduce ability to pause/unpause a cluster: SveltosCluster has a new field called Schedule that allows
  to specify when to unpause a cluster. A Paused SveltosCluster will receive no update from Sveltos.
  This feature so enable having a maintanence window on each managed cluster. Only during this maintanance window, update will be delivered to cluster. For instance, following will have the SveltosCluster set to unpaused only from Friday, 8PM
  to Monday 7AM every week:

sveltosCluster.Spec.Schedule = &libsveltosv1beta1.Schedule{
    From: "0 20 * * 5", // every friday 8PM
    To:   "0 7 * * 1",  // every monday 7AM
}

• When creating a Profile/ClusterProfile with syncMode set to ContinuosWithDriftDetection, adds ability to specify a set
  of fields, for certain resources, to be ignored when evaluation configuration drift. More here. For instance following will have Sveltos ignore changes in Replicas field for any deployment

clusterProfile.Spec.DriftExclusions = []configv1beta1.DriftExclusion{
   {
       Target: &libsveltosv1beta1.PatchSelector{
                       Kind:    "Deployment",
                       Group:   "apps",
                       Version: "v1",
       },
       Paths: []string{"/spec/replicas"},
   },
}

• ability to patch sub resources: referenced ConfigMaps/Secrets/Flux Sources with projectsveltos.io/subresources set indicates Sveltos to patch sub resources.

🌱 Others

• Bump clusterAPI to v1.8.1
• Bump golang to v1.22.5

v0.35.0

🚀 Features:

• TemplateResourceRefs in EvenTrigger instances can be expressed as templates and instantiated using cluster namespace, name, kind. PR
• Referenced resources in EventTriggers (via PolicyRefs or ValuesFrom) can be expressed as template. PR

🐛 Bug Fixes

• SveltosCluster.Status.Ready is set to true first time sveltos cluster controller successfully connects to it. It is never reset to false otherwise. If an issue occurs connecting, only the Status.FailureMessage is updated. PR
• Fix an issue in event-manager not honouring DeploymentType when creating a ClusterProfile. PR

v0.34.2

🐛 Bug Fixes

• template functions (sprig + all others implemented in Sveltos) are moved to libsveltos and so available for both ClusterProfile/Profile and EventTrigger (PR)
• Content of ConfigMap/Secret referenced in ValuesFrom section of both HelmChart and KustomizeRef is considered by Sveltos a template (and so instantiated) only if the referenced ConfigMap/Secret has the projectsveltos.io/template annotation

v0.34.1

🚀 Features:

• EventTrigger spec contains Patches

v0.34.0

🚀 Features:

• customise drift-detection-manager: Sveltos can be passed a ConfigMap containing pre-deployment patches which will be used to customise drift-detection-manager before deploying it. PR
• customize sveltos-agent: Sveltos can be passed a ConfigMap containing pre-deployment patches which will be used to customise sveltos-agent before deploying it. PR

🐛 Bug Fixes

• pre-deployment patches with multiple resources BUG

🌱 Others

• bump clusterapi to v1.7.4

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