We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
From a practical point of view, the service discovery takes place in two places:
Is it expected by design? Why not completely take over service discovery on the CP side
The text was updated successfully, but these errors were encountered:
We explain it in the docs, see here https://github.com/api7/apisix-seed/blob/main/README.md
Sorry, something went wrong.
Let's talk about nacos as a service register.
apache/apisix will do the service discovery, see https://github.com/apache/apisix/blob/bf603ac517e890f2b67c726cc40a66edc58fd8f2/apisix/discovery/nacos/init.lua#L387
And now apisix-seed will do almost the same thing.
How can I disable apisix's service discovery and only use apisix-seed's service discovery?
Just follow this document. https://github.com/api7/apisix-seed/blob/main/docs/en/latest/nacos.md In your apisix configuration, you don’t need to configure any nacos server-related information
No branches or pull requests
From a practical point of view, the service discovery takes place in two places:
Is it expected by design?
Why not completely take over service discovery on the CP side
The text was updated successfully, but these errors were encountered: