Skip to content

Why doesn't Ocelot.Provider.Kubernetes work? #2227

Answered by raman-m
tuannh6495 asked this question in Q&A
Discussion options

You must be logged in to vote

Our extension package is based on KubeClient one.

`message: 'Error Code: ServicesAreEmptyError Message: There were no services in RoundRobin for 'price-webapi' during LeaseAsync operation! errors found in ResponderMiddleware. Setting error response for request path:/api/price/v1/values, request method: GET'

This error means that Kube client either can't connect to the k8s service or it's not configured at all.

If you don't use Pod service then configuration is injected here, and you have to define JSON settings in appsettings.json:

KubeClientOptions options = sp.GetRequiredService<IOptions<Ku…

Replies: 3 comments 4 replies

Comment options

You must be logged in to vote
1 reply
@raman-m
Comment options

Comment options

You must be logged in to vote
1 reply
@raman-m
Comment options

Comment options

You must be logged in to vote
2 replies
@tuannh6495
Comment options

@raman-m
Comment options

Answer selected by raman-m
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
Service Discovery Ocelot feature: Service Discovery Kubernetes Service discovery by Kubernetes
2 participants
Converted from issue

This discussion was converted from issue #2223 on December 02, 2024 09:14.