Skip to content

Conversation

@wind57
Copy link
Contributor

@wind57 wind57 commented Jul 31, 2025

No description provided.

.subscribeOn(Schedulers.boundedElastic());
}

@Override
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

since we use the same properties for the reactive and blocking reactive clients + our reactive clients are based on the blocking ones, we can re-use the order here

}

private Lister<V1Endpoints> setupEndpointsLister(String namespace, V1Endpoints... endpoints) {
private Lister<V1Endpoints> setupEndpointsLister(V1Endpoints... endpoints) {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor simplification that is un-related to the issue itself

@wind57 wind57 changed the title fix order for discovery clients fix 1963: order for discovery clients Jul 31, 2025
@wind57 wind57 marked this pull request as ready for review July 31, 2025 11:26
@wind57
Copy link
Contributor Author

wind57 commented Jul 31, 2025

@ryanjbaxter one more fix ready here. thank you

@ryanjbaxter ryanjbaxter linked an issue Jul 31, 2025 that may be closed by this pull request
@ryanjbaxter ryanjbaxter merged commit 6bd62a3 into spring-cloud:3.2.x Jul 31, 2025
25 checks passed
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

Successfully merging this pull request may close these issues.

KubernetesReactiveDiscoveryClient doesn't respect order

3 participants