Cluster Client Sync Lifecycle

Cluster Client Sync Lifecycle A lifecycle diagram generated by Archify. 01 / Main sync flow 02 / Recovery 03 / Terminal Not onboarded · No record / disabled · Main sync flow · Entry 01 Not onboarded No record / disabled Entry Build ClientSet · buildClientSet · Main sync flow · syncClusters 02 Build ClientSet buildClientSet syncClusters Pick access mode · Credential source · Main sync flow · Three modes 03 Pick access mode Credential source Three modes Client ready · K8s + Prometheus · Main sync flow · ClientSet 04 Client ready K8s + Prometheus ClientSet Build failed · Invalid / unreachable · Recovery · Recoverable Build failed Invalid / unreachable Recoverable Client removed · Cluster record deleted · Terminal · Terminal Client removed Cluster record deleted Terminal Rebuild on change Build failed Retry Cluster deleted / disabled Legend start active state decision terminal success failure / exit neutral

Triggers

  • • Reconciles all clusters every minute
  • • TriggerClusterSync runs a sync immediately

Three access modes

  • • in-cluster / encrypted kubeconfig / agent tunnel
  • • Prometheus URL auto-discovery

Failure and terminal state

  • • A failed build degrades and retries next round
  • • The client is removed when the cluster is deleted