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
An AKS Arc cluster billing status had been out of sync and limited cluster operations.
Sync-AksHciBilling returns Upload Successful! but Get-AksHciBillingStatus | ConvertTo-Json shows a ConnectionStatus OutOfPolicy and the LastConnected date is higher than 30 days.
It is documented in the known issues with the only way to fix as a redeploy with a clean installation.
With help from support, we fixed the issue by deleting the billing-manager pods. kubectl get pods -n azure-arc --kubeconfig (get-kvaconfig).kubeconfig showed the billing-manager deployment older than 76 days
Deleting the pods kubectl delete pod -n azure-arc billing-manager-deployment-597b8997bb-kzksb --kubeconfig (get-kvaconfig).kubeconfig
Sync-AksHciBilling
Fixed the issue and Get-AksHciBillingStatus | ConvertTo-Json reported ConnectionStatus Connected again.
We created multiple workload clusters after initial setup, but did not touch them for more than 60 days.
The text was updated successfully, but these errors were encountered:
An AKS Arc cluster billing status had been out of sync and limited cluster operations.
Sync-AksHciBilling
returnsUpload Successful!
butGet-AksHciBillingStatus | ConvertTo-Json
shows a ConnectionStatusOutOfPolicy
and theLastConnected
date is higher than 30 days.It is documented in the known issues with the only way to fix as a redeploy with a clean installation.
With help from support, we fixed the issue by deleting the billing-manager pods.
kubectl get pods -n azure-arc --kubeconfig (get-kvaconfig).kubeconfig
showed the billing-manager deployment older than 76 dayskubectl delete pod -n azure-arc billing-manager-deployment-597b8997bb-kzksb --kubeconfig (get-kvaconfig).kubeconfig
Sync-AksHciBilling
Get-AksHciBillingStatus | ConvertTo-Json
reported ConnectionStatusConnected
again.We created multiple workload clusters after initial setup, but did not touch them for more than 60 days.
The text was updated successfully, but these errors were encountered: