Using Audit Logs to Track Changes in Fleet or ArgoCD

Wed, 11 Sep 2024 02:26:00 -0500

In environments where GitOps tools like Fleet or ArgoCD are used to manage Kubernetes clusters, changes can be rapid and automated. However, when things go wrong—such as deployments failing, or configurations being overwritten—it’s important to know who made the change, what was changed, and when the change occurred.

In this post, we’ll focus on how you can use audit logs from Rancher, Fleet, and ArgoCD to track down the root cause of issues. We’ll walk through practical examples, and show you how to trace changes back to the IP address or user responsible.

Fleet on Support Tools

Using Audit Logs to Track Changes in Fleet or ArgoCD