v0.40.0

🚀 Features

• Dashboard support for multi-tenancy: users can login using bearer token and can only see clusters they have permissions for
• Add-on controller caches remote managed clusters' clients

v0.39.0

🚀 Features

• Expose serviceAccount info that Sveltos should use when renewing token
• Expose SkipSchemaValidation in HelmChart options

🐛 Bug Fixes

• Remove resources created in the management cluster when a managed cluster is deleted. Bug
• Avoid incorrect logs about compatibility checks in the management cluster. Bug

v0.38.4

🐛 Bug Fixes

• Resolve issue preventing add-on installation on clusters after deletion and recreation.

v0.38.3

🚀 Features

• Helm charts: add ability to upgrade CRDs during helm release upgrade

🐛 Bug Fixes

• Fix add-on-controller crash when in ContinuousWithDriftDetection mode

v0.38.2

🐛 Bug Fixes

• Fix for private registries

v0.38.1

🌱 Others

• Bump clusterAPI to v1.8.3
• golang v1.22.7

v0.38.0

🚀 Features

• introduce compatibility checks: to ensure seamless operation, Sveltos implements compatibility checks between its services in the management cluster and those deployed in managed clusters. The management cluster's services rely on data generated by Sveltos agents and drift-detection managers in the managed clusters. When Sveltos is upgraded, the management cluster's services are updated first. These services then initiate the upgrade process for Sveltos services in each managed cluster. Before allowing the management cluster's services to consume data from upgraded managed clusters, compatibility checks verify that all Sveltos services are running the same version.
• add support to pull Helm charts from private registries

🌱 Others

• Bump clusterAPI to v1.8.2

v0.37.0

🚀 Features:

• Generators: add ability to create resources in the management cluster in response to events. The naming convention for these generated ConfigMaps and Secrets is defined by the InstantiatedResourceNameFormat setting. This approach guarantees a predictable name for each generated resource.

🐛 Bug Fixes

• Use clusterAPI utility to fetch Kubeconfig for a CAPI clusters. Previously Sveltos assumed the Secret had only one key/value pair containing the kubeconfig. Fix
• react to referenced ConfigMap/Secret/Sources annotation changes. Fix

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