wolgod commented on issue #7791: URL: https://github.com/apache/apisix/issues/7791#issuecomment-1227122950
> Hi , @wolgod > > > If I use the kubernetes service discovery function, is there an interface to get the real Upstream information on the backend of the service, or is this information just cached in the apisix instance and cannot be viewed? > > there is no interface for dump now ,welecom PR . > > > in the documentation, it is said that the data exists in ngx.shared.kubernetes. If my apisix instance is restarted, how can I ensure that all Upstreams have been re-acquired before processing the request? > > kubernetes discovery uses List-Watch to get endpoint information . > > upstreams information is empty until the first "List" complete . If there is a querying before completed, it will get an "nil" result > > If you cannot accept this, you may need some way to ensure that apisix only accepts client requests after kubernetes discovery completing first "List". ApiSix can't do this by its own thanks for answer, about second problem 1. In my understanding, the list-watch should be in the master worker. If I execute apisix reload, it should not cause the list-watch to be re-listed. I don’t know if it is correct. 2. After the first list in k8s is completed, all endpoints will be obtained. At this time, the service should be able to obtain upstreams, but when will the first list be completed, there will be log printing or is there any other way to obtain it -- 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]
