ArgoCD › Multi-cluster

How do you handle credentials rotation for many clusters?

Advanced

Answer

Automate rotation of the service-account tokens/kubeconfigs stored in cluster Secrets, prefer short-lived credentials via cloud identity (IRSA, Workload Identity), and manage the Secrets through External Secrets so rotation happens centrally without manual edits. Monitor for expired credentials causing Unknown status.
Real-world example Cluster access uses workload identity so tokens are short-lived and rotate automatically without manual Secret edits.

Common follow-ups: Why prefer short-lived credentials? | How does External Secrets help rotation?