-
Notifications
You must be signed in to change notification settings - Fork 1k
Fix 1641 issue with wiring + k8-native discovery cacheable implementation #2071
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
Fix 1641 issue with wiring + k8-native discovery cacheable implementation #2071
Conversation
Signed-off-by: wind57 <[email protected]>
…ces' into fix-1641-make-k8s-client-discovery-client-cacheable
Signed-off-by: wind57 <[email protected]>
Signed-off-by: wind57 <[email protected]>
…ces' into fix-1641-make-k8s-client-discovery-client-cacheable
Signed-off-by: wind57 <[email protected]>
Signed-off-by: wind57 <[email protected]>
…to fix-1641-issue-with-wiring
Signed-off-by: wind57 <[email protected]>
Signed-off-by: wind57 <[email protected]>
| return new Fabric8ReactiveDiscoveryClient(fabric8DiscoveryClient); | ||
| } | ||
|
|
||
| @Bean |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we have a situation where there are two discovery clients options:
- cacheable
- non-cacheable
If we enable the cacheable one, the health indicator is going to fail, since it expects a non-cacheable one.
I did not catch that initially since there was no test to cover that, now there is.
Signed-off-by: wind57 <[email protected]>
|
@ryanjbaxter this adds k8s-client cacheable discovery implementation + fixes a small issue |
|
Will the documentation come in a separate PR? |
|
Yes, in the next one |
No description provided.