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
Sometimes there are non-Rancher initiated updates triggered by the console, this information is logged in the deployment logs, but there is no way to know if that is the case otherwise.
It would make sense to update the cluster state, or add a new field to indicate non-rancher initiated update is in progress.
│ aks-config-operator-7c4b55584-mtdvc:time="2025-01-14T15:22:11Z" level=info msg="Waiting for non-Rancher initiated cluster update for [auto-aks-pvala-hp-ci-mdbmf (id: c-qbrgg)]" │
The text was updated successfully, but these errors were encountered:
Sometimes there are non-Rancher initiated updates triggered by the console, this information is logged in the deployment logs, but there is no way to know if that is the case otherwise.
It would make sense to update the cluster state, or add a new field to indicate non-rancher initiated update is in progress.
The text was updated successfully, but these errors were encountered: