v0.8.0

🚀 Features

• events and healt checks fully integrated with sveltos multi tenancy solution. This means a tenant admin can create EventSource/HealthCheck/EventBasedAddOns and Sveltos will make sure user can evaluate only resources it has been granted access by platform admin (via sveltos RoleRequest). Sveltos agent running on managed clusters will achieve it by impersonating the tenant when fetching resources (so Kubernetes RBAC will end up validate permissions).
• cross cluster configurations: in response to an event happening in a cluster, Sveltos allows deploying add-ons in the very same cluster event happened or request add-ons to be deployed in a different set of clusters.
• snapshot collects also EventSources/EventBasedAddOns/HealthChecks

v0.7.2

Fixes:

• Add support for Lua script in Classifier
• Fix event-manager RBAC (permission to create/update/delete secrets)

v0.7.1

• Fix sveltos manager core
• Fix event manager handling when oneForEvent field is set to false

v0.7.0

🚀 Features

1. event driven add-on deployments: define an event and what add-ons need to deployed when event is detected. Add-ons can be expressed as template. When an event is detected in managed cluster, Sveltos will instantiate (if needed) and deploy add-ons;
2. cluster health check: define an health check passing Sveltos a Lua script. Sveltos will keep watching resources in a managed clusters and keeps evaluating the cluster health. When cluster health changes, Sveltos sends a notification (Webex and/or Slack message and/or a Kubernetes event).

v0.6.0

🚀 Features

• Techsupport: sveltos can collect tech support (both logs and resources) from managed clusters
• Add support to send webex notifications

v0.5.0

🚀 Features
• Introduce cluster liveness checks. Ability to receive a notifications (either a Kubernetes event of type reason=ClusterHealthCheck or a slack notification) when Kubernetes add-ons are provisioned in a cluster.

🐛 Bugs
• Fix a bug that prevented add-ons to be provisioned if Cluster (with proper labels) was created after ClusterProfile

v0.4.1

🚀 Features

• ConfigMaps/Secrets referenced by ClusterProfile and RoleRequest can be set with an empty namespace. When namespace is empty, at the time of deployment, Sveltos will find ConfigMap/Secret in the cluster namespace.

⚠️ Breaking Changes

• Secret referenced by ClusterProfile and RoleRequest must be of type addons.projectsveltos.io/cluster-profile

v0.4.0

🚀 Features

• multi-tenancy

🌱 Others

• bump cluster-api pin to v1.3.3

v0.3.0

🚀 Features

• register existing, non clusterAPI, clusters;
• configuration drift detection

🌱 Others

• bump cluster-api pin to v1.3.1

🐛Bug fixes

• fix a classifier crash when cluster had no labels;
• fetch Kubernetes version by using k8s.io/client-go/discovery instead of relying on node labels