bzp2010 commented on issue #2542: URL: https://github.com/apache/apisix-ingress-controller/issues/2542#issuecomment-3249945101
@taherbohri In standalone deployments, health checks should actually be performed by Kubernetes probes and exposed to applications through Kubernetes services and endpoints. The Ingress Controller is responsible for tracking the endpoint/endpointslice associated with every active Kubernetes service, where the corresponding pod IP is stored. When a pod is not in a ready state, it will not appear in this list until the probe informs Kubernetes that it is ready. In most cases, APISIX neither needs nor should use its built-in health check capabilities (when using Ingress Controller). Instead, Kubernetes' native capabilities should be utilized first. Only when these prove completely inadequate should APISIX's options be considered. For the reasons stated above, I have decided that the underlying technology of the Ingress Controller (ADC) does not support this option. Currently, this is an artificial limitation that may be lifted in the future based on actual requirements. ref: https://github.com/api7/adc/blob/main/libs/backend-apisix-standalone/README.md#differences-in-upstream If you have more compelling reasons, you may present them to persuade me to reconsider this decision. -- 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]
