-
Notifications
You must be signed in to change notification settings - Fork 25
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
New service discovery implementation based on Knative #402
Comments
Followed up by quarkusio/quarkus-upstream-roadmap#19. organization: QuarkusIO
repository: quarkus-upstream-roadmap
issue: 19
url: https://github.com/quarkusio/quarkus-upstream-roadmap/issues/19 |
aureamunoz
added a commit
to aureamunoz/smallrye-stork
that referenced
this issue
Nov 28, 2022
aureamunoz
added a commit
to aureamunoz/smallrye-stork
that referenced
this issue
Dec 12, 2022
aureamunoz
added a commit
to aureamunoz/smallrye-stork
that referenced
this issue
Dec 13, 2022
aureamunoz
added a commit
to aureamunoz/smallrye-stork
that referenced
this issue
Dec 16, 2022
aureamunoz
added a commit
to aureamunoz/smallrye-stork
that referenced
this issue
Dec 30, 2022
aureamunoz
added a commit
to aureamunoz/smallrye-stork
that referenced
this issue
Jan 9, 2023
cescoffier
pushed a commit
that referenced
this issue
Jan 9, 2023
Implement knative service discovery Fixes #402 - fix: setup knative service data properly in test - Fix revapi configuration - Explain differences between Knative and K8s according to review
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We would need a new service discovery implementation in Stork for KNative. This SD locates the KNative service (and not the pods as we do for Kubernetes). It would not be possible to use load balancing. However, if you use KNative, load balancing can be handled there.
This SD would take a (Knative) service name as parameter and search for it in the current (or configured) namespace. It will not check if there are pods, just locate the service, resolve the name and return that name. It fails if no service can be found. You will never have more than one service (this needs to be verified when using revisions).
See Quarkus #146
The text was updated successfully, but these errors were encountered: