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

support dual stack address registry and discovery in Spring Cloud Netflix Eureka #4295

Open
lc0138 opened this issue Jul 29, 2024 · 0 comments

Comments

@lc0138
Copy link

lc0138 commented Jul 29, 2024

Hi Spring Cloud Team,
We are using Spring Cloud Netflix as our Discovery Service, and also setup an Eureka cluster as registration center.

We need to provide a method to help enterprises realize the smooth migration of the large-scale Spring Cloud microservice system IP address stack from IPv4 to IPv6. The specific method is to achieve migration through dual registration and double subscription. The specific migration steps of this solution are as follows:

  1. First, upgrade the Spring Cloud framework for all microservice applications in the system to enable them to have dual-stack address extraction and resolution functions.
  2. Transform the IP address protocol stack of the host machine where some microservices in the system are located, so that it supports dual-stack IPv4 and IPv6 addresses at the same time.
  3. The dual-stack address extraction module in the microservice application modified in step 2 extracts the dual-stack addresses in the application host, and registers the dual-stack addresses to the registration center through the service registration module.
  4. Consumers subscribe to the dual-stack IPv4 and IPv6 addresses of a service in the registration center, and compare the address stack types supported by the host through the dual-stack address resolution module in the application. If the host only supports IPv4, use The provider’s IPv4 address initiates a service call; if only IPv6 is supported or dual-stack is supported at the same time, the provider’s IPv6 address is used to initiate a service call. If the call fails, it is best to use the IPv4 address to retry.
  5. When all Spring Cloud microservices in the system have completed supporting the IPv6 address stack, gradually close the IPv4 address stack for all application hosts, thereby smoothly completing the migration of the large-scale microservice system from the IPv4 address stack to the IPv6 address stack.

This solution has been finished in Spring Cloud Alibaba, and it only supports Nacos registration center, don't supports Eureka. Do you have any plans to support Eureka in Spring Cloud Netflix?

Thanks very much.

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

No branches or pull requests

3 participants