In #262 flux-commit-tracker was enabled to watch all Kustomizations in a cluster so that it could use reconciliation events from each to generate the flux_commit_tracker_e2e_export_time_seconds metrics. However, since all Kustomizations reconcile within seconds of each other after a new OCI image lands in the cluster, we really only need to watch the Kustomization that manages flux-commit-tracker. This will essentially restore the previous functionality of the tracker in terms of how it determined the "end time" of the end-to-end metrics generated for each deployment_tools commit in a KME master export.
In #262
flux-commit-trackerwas enabled to watch all Kustomizations in a cluster so that it could use reconciliation events from each to generate theflux_commit_tracker_e2e_export_time_secondsmetrics. However, since all Kustomizations reconcile within seconds of each other after a new OCI image lands in the cluster, we really only need to watch the Kustomization that managesflux-commit-tracker. This will essentially restore the previous functionality of the tracker in terms of how it determined the "end time" of the end-to-end metrics generated for eachdeployment_toolscommit in a KME master export.