kubewatch

When several people or automated systems change a cluster, it can be difficult to notice which resource was created, updated or removed. Kubewatch watches selected Kubernetes objects and sends notifications to configured destinations, such as a team chat or webhook receiver. That gives operators a convenient stream of activity to investigate. It is a notification tool, not a permanent audit record; this entry also distinguishes the original Bitnami project from its documented continuation.

Current guidance

The original Bitnami project now appears under vmware-archive/kubewatch. Its README states that VMware no longer maintains it and directs users to robusta-dev/kubewatch. The latter identifies itself as the continuation and documents watching Kubernetes resource changes and sending notifications to several supported endpoints.

Evaluate the continuation’s chart and application image together; do not assume an old Bitnami image or stable-chart values are interchangeable with its current packaging. Choose which resource types and namespaces produce events, and confirm the actual filtering capabilities rather than relying on a similarly named alerting product.

Notifications are not a durable Kubernetes audit log. Decide what must be retained elsewhere, how duplicates and delivery failures are handled and whether resource details can expose secrets to a chat or webhook service. Scope watcher RBAC and destination credentials, then test creation, update and deletion of a disposable resource plus an unavailable receiver. The repository continuation is verified; current compatibility and operational behavior still depend on the exact release and configuration selected.