v0.47.0

🚀 Features

• Dashboard: it is now possible to see all profiles grouped by tiers. By selecting a single profile, dashboard will display dependencies and dependents as well as list of matching clusters and status
• Use image digest instead of tags when deploying Sveltos via HelmCharts
• More robust handling of token renewal. More here

v0.46.1

🐛 Bug Fixes

• Set SveltosCluster mgmt/mgmt token renewal to one hour. Release v0.46.0 set it to 3 hours causing problem on upgrades. More info here
• Copy SyncMode from EventTrigger Spec to ClusterProfile Spec. bug
• Allow CloudEventAction to be expressed as a template. This allow action (Create or Delete) to be decided at run time using CloudEvent. More info PR

v0.46.0

Features

• EventSource can now match CloudEvents received over NATS/JetStream. More here and here
• Lua can be used to generate at run time what needs to be deployed. It is an alternative to go templating.  More here
• Sveltos, by default, deploys Helm charts and resources in the order they appear in a ClusterProfile/Profile, retrying on errors
  without proceeding to subsequent deployments. For example, if a ClusterProfile lists three Helm charts and the second fails to deploy,
  Sveltos will not attempt to deploy the third. However, enabling the Spec.ContinueOnError setting allows Sveltos
  to proceed with deploying the third Helm chart and then retry the failed second chart. More here
• When registering the management cluster, Instead of generating a token with an expiration, the token is taken from a Secret of type kubernetes.io/service-account-token. More here

Bug Fixes

• When running in agent less mode (Sveltos agent and drift detection deployed in the management cluster for each managed cluster), those agent t receive the managed cluster's kubeconfig from a Secret. These kubeconfigs can expire (e.g., GKE tokens have a maximum lifespan of 48 hours). Sveltos includes a mechanism to proactively renew these tokens. The SveltosCluster controller can be configured to periodically refresh tokens before they expire, preventing disruptions. However the drift-detection controller and Sveltos-agent when deployed in the management cluster, lacked the ability to retrieve an updated kubeconfig. Consequently, upon kubeconfig
  expiration, the controller encountered numerous authorization errors, effectively ceasing operation. More here and here
• Fix an issue fetching helm charts from not OCI-compliant private registries. More here

v0.45.0

🚀 Features

• introducing techsupport feature
• adding telegram and mail as notification options

v0.44.0

🚀 Features

• dryRun mode: for each helm charts, Sveltos will report detailed helm value diff. PR
• clusterProfile helmCharts section can be expressed as a template. PR
• templateResourceRefs: namespace can now also be expressed as a template. PR

🐛 Bug Fixes

• enforces StopMatching values. PR

v0.43.0

🚀 Features

• New set of template functions: copy, setField, removeField, chainSetField, chainRemoveField
• dry run full diff: when running with SyncMode DryRun, Sveltos can display full diff for resources that would be updated by the proposed change

🐛 Bug Fixes

• Reconcile EventTrigger instances when referenced resources change. PR

v0.42.1

🐛 Bug Fixes

• Fix a bug with DeploymentType set to Local in Profile instances. [Bug](deploymentType: Local does not work with Profile)
• Fix a bug that prevented EventManager to react to changes in ConfigMap/Secret instances referenced by Generator. PR

v0.42.0

🚀 Features

• Add telemetry

v0.41.1

🚀 Features

• Allow to specify the kubeconfig key in a Secret

v0.41.0

🐛 Bug Fixes

• Event manager reacts to ConfigMap/Secret changes PR
• Better handle scenarios when matching cluster is deleted PR
• Better handles helm chart conflicts PR