One workload has two types of azure-wi-webhook-controller-manager in two different namespaces.

[RamPrasad-18]

I need a resolution for the following error. There are two different namespaces with one workload identity naming convention. One of them is encountering a recurring CrashLoopBackOff error.

Error details:

12/21/2024, 7:45:02.582 AM
aks-pool01-14553242910-vmss000004
7914cf47fa914530ar4rxeder4tfr43b7d1293fcef67add15fb49dde
manager
azure-wi-webhook-controller-manager-d5db8fd64-6pcpb
azure-workload-identity-system
E1221 07:45:02.577592 1 main.go:149] entrypoint "msg"="unable to run manager" "error"="failed to wait for cert-rotator caches to sync: timed out waiting for cache to be synced"
TenantId
39ed8df7-74c0-43ww-89ea-593ace6343fb
Computer
aks-pool01-de4r4-vmss000004
ContainerId
7914cf47fa94eder4ferddede15fb49dde
ContainerName
manager
PodName
azure-wi-webhook-controller-manager-d5db8fd64-6pcpb
PodNamespace
azure-workload-identity-system
LogMessage
E1221 07:45:02.577592 1 main.go:149] entrypoint "msg"="unable to run manager" "error"="failed to wait for cert-rotator caches to sync: timed out waiting for cache to be synced"
LogSource
stderr
TimeGenerated [UTC]
2024-12-21T07:45:02.5829582Z
LogLevel
error
Type
ContainerLogV2