bzp2010 commented on PR #12179: URL: https://github.com/apache/apisix/pull/12179#issuecomment-2857758081
@nic-6443 > Yes, this is exactly what we need to avoid. External programs require time to know the new APISIX instance going online or an existing instance restarting. Before the external program commits the configuration for the first time, this APISIX instance does not have the capability to provide services externally. Therefore, we need a mechanism to provide the health status of APISIX, especially in this new API-driven standalone mode. Oh, I see. You are saying that this data plane should not report to Kubernetes that it is in a READY state to prevent the load balancer from distributing traffic to it until the ingress controller commits its first configuration. -- 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: notifications-unsubscr...@apisix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
