时间戳

首页 > 解决方案 > 为什么 Nginx 控制器提供 Scheduled for sync？

kubernetes-ingress - 为什么 Nginx 控制器提供 Scheduled for sync？

问题描述

我已经部署了 AWS alb 和 nginx-controller。我正在使用 nginx 将流量路由到 diff 命名空间。当我应用入口资源并描述时，我得到

----    ------  ----               ----                      -------
  Normal  Sync    42m (x4 over 72m)  nginx-ingress-controller  Scheduled for sync
  Normal  Sync    42m (x4 over 72m)  nginx-ingress-controller  Scheduled for sync
  Normal  Sync    42m (x4 over 72m)  nginx-ingress-controller  Scheduled for sync
  Normal  Sync    42m (x4 over 72m)  nginx-ingress-controller  Scheduled for sync

我无法击中主机。但它与其他主机合作良好。

kubectl describe ing XXXXX 

Name:             promethues-ingress-dev
Namespace:        monitoring
Address:          172.20.223.123
Default backend:  default-http-backend:80 (<error: endpoints "default-http-backend" not found>)
Rules:
  Host                     Path  Backends
  ----                     ----  --------
  dashboard.dev.xxxx.ai
                           /*   kube-prom-stack-dev-grafana:80 (10.0.1.189:3000)
Annotations:               kubernetes.io/ingress.class: nginx
                           nginx.ingress.kubernetes.io/rewrite-target: /
Events:
  Type    Reason  Age                From                      Message
  ----    ------  ----               ----                      -------
  Normal  Sync    42m (x4 over 72m)  nginx-ingress-controller  Scheduled for sync
  Normal  Sync    42m (x4 over 72m)  nginx-ingress-controller  Scheduled for sync
  Normal  Sync    42m (x4 over 72m)  nginx-ingress-controller  Scheduled for sync
  Normal  Sync    42m (x4 over 72m)  nginx-ingress-controller  Scheduled for sync

标签： kubernetes-ingressnginx-ingress

解决方案

就我而言，在将 Nginx 升级到 v1 后，我遇到了 Nginx-controller 无法建立领导者的问题，这是由于领导者选举配置图的名称发生了变化。

https://github.com/kubernetes/ingress-nginx/issues/7632。

确保在更新 Nginx 时，也会更新关联的角色权限。

推荐阅读