silence8013 opened a new issue, #2579: URL: https://github.com/apache/apisix-ingress-controller/issues/2579
### Current Behavior The ingress resource does not update status.loadBalancer.ingress, which will cause the ingress resource status in argocd to be processing。 see kubernete ingress resource： <img width="924" height="1518" alt="Image" src="https://github.com/user-attachments/assets/e497490f-12d6-4f32-944b-f8ab2dd9030f"; /> argocd ingress status： <img width="2368" height="1078" alt="Image" src="https://github.com/user-attachments/assets/8c38d030-7d00-449e-9630-2f8aecd1fcec"; /> ### Expected Behavior kubernete ingress resource： <img width="948" height="1588" alt="Image" src="https://github.com/user-attachments/assets/3426cbe1-47d1-4fac-b205-36c06a06fd5f"; /> argocd ingress status： <img width="2474" height="1174" alt="Image" src="https://github.com/user-attachments/assets/dc74820c-15d9-4711-bdee-aef5135680b0"; /> Cause of the problem： The gatewayProxy in the apisix ingress controller helm chart does not define a publishService if apisix is deployed in a k8s cluster. I configured publishService and the problem was restored。 <img width="1168" height="892" alt="Image" src="https://github.com/user-attachments/assets/23ea6db2-e841-4702-ad61-ae7886e91d63"; /> <img width="1504" height="1602" alt="Image" src="https://github.com/user-attachments/assets/4a639387-5f94-47b7-8073-383f4a212e57"; /> ### Error Logs no ### Steps to Reproduce 1. install apisix ingress controller with the helm chart. 2. use argocd create ingress resource. ### Environment - APISIX Ingress controller version (run `apisix-ingress-controller version --long`) 2.0.4rc - Kubernetes cluster version (run `kubectl version`) 1.34 - OS version if running APISIX Ingress controller in a bare-metal environment (run `uname -a`) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
