Skip to content
New issue

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

Question about service discovery #69

Open
warrenincn opened this issue Feb 15, 2023 · 3 comments
Open

Question about service discovery #69

warrenincn opened this issue Feb 15, 2023 · 3 comments

Comments

@warrenincn
Copy link

From a practical point of view, the service discovery takes place in two places:

  1. apisix discovery module;
  2. apisix-seed;

Is it expected by design?
Why not completely take over service discovery on the CP side

@soulbird
Copy link
Contributor

We explain it in the docs, see here https://github.com/api7/apisix-seed/blob/main/README.md

@warrenincn
Copy link
Author

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?

@soulbird
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants