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
Deploy NIC v5.0.0 with zone-sync: true in configmap.
Check if the headless svc is created and there are no resolver related errors in NIC logs,
Upgrade NIC to latest available edge build keeping the zone-sync: true in configmap
Check the NIC logs and observe as the headless service fails to get resolved by dns resolver
2025/06/05 10:24:10 [error] 24#24: test-release-nginx-ingress-controller-replicaset-hl.default.svc.cluster.local could not be resolved (3: Host not found)
2025/06/05 10:24:16 [error] 24#24: test-release-nginx-ingress-controller-replicaset-hl.default.svc.cluster.local could not be resolved (3: Host not found)
Possible cause is difference in the selectorLabels of headless service and new replicaset as the service doesn't gets recreated, removing the service manually fixes the issue as the new one gets created by controller with updated labels (specifically pod-template-hash)
Uh oh!
There was an error while loading. Please reload this page.
Version
edge
What Kubernetes platforms are you running on?
GKE Google Cloud
Steps to reproduce
zone-sync: true
inconfigmap
.zone-sync: true
inconfigmap
Possible cause is difference in the selectorLabels of headless service and new replicaset as the service doesn't gets recreated, removing the service manually fixes the issue as the new one gets created by controller with updated labels (specifically pod-template-hash)
replicaset:
svc:
The text was updated successfully, but these errors were encountered: