-
Notifications
You must be signed in to change notification settings - Fork 15
[Feature] Notifications
Notifications will alert users when clusters, or an object deployed into the cluster are no longer compliant. Compliance could be caused by the object changing in git, or a change made on the cluster.
Some of the biggest challenges to adopting a completely automated environment that leverages declarative management are organizational barriers associated with adopting the tools and associated practices. And in some scenarios, finding the win/win that enhances existing requirements such as audit trails for regulatory compliance, with scale and agility. Simply put, installing ArgoCD or Flux and having it deploy applications or Kubernetes objects such as RBAC policies isn't going to magically change how a business runs, nor are they going to remove the barriers to adoption.
Arlon looks to reduce the barriers to adopting a declarative management approach by enabling incremental organizational change, one significant feature that enables this are ArgoCD Notifications, now core to ArgoCD, Arlon will allow users to implement notifications for ClusterSpec, Profile and Bundles. Such that if either the sync state of the Application changes a notification will be sent out that communicates the issue.
When a user creates a cluster they will be able to specify it notifications should be enabled and for which objects notifications should be sent for. The following list outlines notification support
- All -> Any of clusterSpec, Profile or Bundle
- clusterSpec -> if the clusters configuration is changed either on the cluster, the management cluster or in Git
- Profile -> notifications will be sent when bundles are added/removed or found to be missing.
- Bundle -> more of an app level item, notifications can be sent when the bundle is out of sync.
- Open item: Should health state be included? '2022/06/01'