Skip to content

[Bug]: Upgrade from 5.0.0 to edge causes zone-sync to fail #7864

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
vepatel opened this issue Jun 5, 2025 · 1 comment · May be fixed by #7865
Open

[Bug]: Upgrade from 5.0.0 to edge causes zone-sync to fail #7864

vepatel opened this issue Jun 5, 2025 · 1 comment · May be fixed by #7865
Assignees
Labels
backlog Pull requests/issues that are backlog items bug An issue reporting a potential bug

Comments

@vepatel
Copy link
Contributor

vepatel commented Jun 5, 2025

Version

edge

What Kubernetes platforms are you running on?

GKE Google Cloud

Steps to reproduce

  1. Deploy NIC v5.0.0 with zone-sync: true in configmap.
  2. Check if the headless svc is created and there are no resolver related errors in NIC logs,
  3. Upgrade NIC to latest available edge build keeping the zone-sync: true in configmap
  4. 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)

replicaset:

Selector:       app.kubernetes.io/instance=test-release,app.kubernetes.io/name=nginx-ingress,pod-template-hash=65db4857d8

svc:

Selector:                 app.kubernetes.io/instance=test-release,app.kubernetes.io/name=nginx-ingress,pod-template-hash=7df8445684
@vepatel vepatel added bug An issue reporting a potential bug backlog Pull requests/issues that are backlog items labels Jun 5, 2025
Copy link

github-actions bot commented Jun 5, 2025

Hi @vepatel thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

Cheers!

@vepatel vepatel linked a pull request Jun 5, 2025 that will close this issue
6 tasks
@vepatel vepatel moved this from Todo ☑ to In Progress 🛠 in NGINX Ingress Controller Jun 5, 2025
@vepatel vepatel self-assigned this Jun 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Pull requests/issues that are backlog items bug An issue reporting a potential bug
Projects
Status: In Progress 🛠
Development

Successfully merging a pull request may close this issue.

1 participant