--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/45fd9973-f4ef-4d3a-8dfc-42f584dfd6a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You can create your own as well: https://vertx.io/docs/vertx-service-discovery/java/#_implementing_your_own_service_typeWhich doc did you take a look at?There is a list of builtin service types on the website: https://vertx.io/docs/vertx-service-discovery/java/#_types_of_services
2018-04-17 20:53 GMT+02:00 <elr1c...@gmail.com>:
Looking at the doc of vertx service discovery, I understand that it is only possible to retrieve http-endpoints services with kubernetes.However, looking at this repository, I can see that it is possible to retrieve a redis endpoint too : https://github.com/cescoffier/vertx-devoxxfr-2017/blob/master/shopping-backend/src/main/java/me/escoffier/demo/ShoppingBackend.javaSo, I am not sure to have understood what is exactly possible to do or not with vertx service discovery bridge for Kubernetes. Actually, I would also like to retrieve services of type EventBusService or MessageSource registered on Openshift. All my services communicate via the event bus, not via http.Is it possible ?Thanks by advance.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/febaf9f9-4307-4cf0-adca-4a9c046faaea%40googlegroups.com.
On 18 Apr 2018, at 10:37, Thomas SEGISMONT <tsegi...@gmail.com> wrote:The Kubernetes *bridge* is a tool to _import_ Kubernetes services into Vert.x service discovery. As of Vert.x 3.5.1, it only supports importing Kubernetes HTTP services.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/CACiEr_S95vp3OhQf-j8uY%3DnEmXmX-Bgk_gL6YOXQd2z%2BtBt-iw%40mail.gmail.com.
On 18 Apr 2018, at 10:37, Thomas SEGISMONT <tsegi...@gmail.com> wrote:The Kubernetes *bridge* is a tool to _import_ Kubernetes services into Vert.x service discovery. As of Vert.x 3.5.1, it only supports importing Kubernetes HTTP services.As well as various databases (mongo, redis, mysql, postgres…).
Clement
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/CACiEr_S95vp3OhQf-j8uY%3DnEmXmX-Bgk_gL6YOXQd2z%2BtBt-iw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/EDE779BB-92CB-4D67-997F-48765E295327%40gmail.com.
On 18 Apr 2018, at 16:35, Thomas SEGISMONT <tsegi...@gmail.com> wrote:2018-04-18 16:13 GMT+02:00 Clement Escoffier <clement....@gmail.com>:On 18 Apr 2018, at 10:37, Thomas SEGISMONT <tsegi...@gmail.com> wrote:The Kubernetes *bridge* is a tool to _import_ Kubernetes services into Vert.x service discovery. As of Vert.x 3.5.1, it only supports importing Kubernetes HTTP services.As well as various databases (mongo, redis, mysql, postgres…).So this doc section should be updated: https://vertx.io/docs/vertx-service-discovery/java/#_kubernetes_bridge ?
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/CACiEr_RBYkWpLgbo%3DgM2XD_xpSM__jUG_mN%3DVbyKayaK9RbPow%40mail.gmail.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/CACiEr_RBYkWpLgbo%3DgM2XD_xpSM__jUG_mN%3DVbyKayaK9RbPow%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/BE5F7B41-B0E0-40F4-AD8F-C3769A1FBDE8%40gmail.com.
On 30 Apr 2018, at 22:19, elr1c...@gmail.com wrote:Hi Thomas,sorry, I was on holidays last week.I saw Clement already did the fix, it is very good.However, I have 2 other questions about service discovery (not only Kubernetes one) :
- does service discovery supports load balancing ? according to this issue, it does not. Maybe it would be useful to add it in the doc too.
- how do you manage tests (unit and integration) with ServiceDiscovery.create calls ?
Thanks by advance.--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/ba08adb1-a6d0-4d1c-938f-0bd8030ea97b%40googlegroups.com.
- how do you manage tests (unit and integration) with ServiceDiscovery.create calls ?
You mean to inject services in your tests? You can register service explicitly using the `publish` method.