You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: propagate registry auth secret to Fleet workspaces on rotation
The SettingsReconciler wrote the registry basic-auth secret (e.g.
ngc-helm-auth) only to cattle-system. The Fleet-workspace copies that
HelmOps reference via helmSecretName were written per-workload by
ensureFleetAuthSecret, which only runs on an AIWorkload reconcile — not
on a key rotation. So a rotated NGC key left fleet-local/fleet-default
stale, and gated blueprint installs failed with a 403 reading the helm
index. Write the auth secret to all consuming namespaces (cattle-system +
fleet-local + fleet-default) so a rotation propagates in one reconcile;
the existing Secret watch already triggers it. Delete from all on prune.
0 commit comments