Daniel Lavoie

Hi ! I understand Feign has not been designed with non blocking in mind. Maybe a new project is a better target. I would suggest using reactive stream as a...

Thanks @adriancole sounds interesting. I'll check it out.

I came to realize that my proposed solution will not work since I wrongly interpreted that the chart would create a distinct service per port definition. Turns out the only...

@SantoDE I'm facing a dilema. Either I run two distinct traefik instance with different service annotations or I break the configuration values of `service.xxxx`. Supporting multiple services with an opt-in...

I like the idea of a `@LeaderOnly` annotation. On another aspect, this leader election system implies some coupling to the underlying election implementation (in this issue we are talking about...

I've been thinking on how to implement such `@LeaderOnly` on a `@Scheduled` method. I'm clueless because the `ScheduledAnnotationBeanPostProcessor` checks for the presence of `@Scheduled` and registers the tasks for execution....

I went a little further with an implementation and realized that using Spring `EventListener` to react to a LeaderElection composed with a `@Scheduled` is something really dangerous for race conditions....

I've got exactly the same symptoms described by @eembsen. Any reasonable explanation on this? Why would the DNS problems occur only for the containers spawned by our tasks?

From the stack trace you should understand that this issue is a pure Feign problem. Spring Cloud Netflix facilitate Netflix OSS component integration into Spring. I would suggest you to...

You are right. Looks like I had a bad understanding of Spring Cloud Feign. I'll try to have a look and see if I can come up with a trick...