You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we think about what is done with Consul and Tiller, we might agree that we will, somehow, generate configurations for each available service in consul and rigister it in a configuration file for some service like nginx / whatever as an upstream server - generating the configuration will be done by tiller.
No, with the current consul_services the health status is not respected, its just all available service, no matter if they answer or not. This collection, together with the use of a live registry like consul will then generated broken upstream services.
I cannot image a single usecase where this makes actual sense.
I would suggest, we either reimplement consul_services to include only health services or we introduce consul_services_healthy as an additional variable for that.
If we think about what is done with Consul and Tiller, we might agree that we will, somehow, generate configurations for each available service in consul and rigister it in a configuration file for some service like nginx / whatever as an upstream server - generating the configuration will be done by tiller.
No, with the current consul_services the health status is not respected, its just all available service, no matter if they answer or not. This collection, together with the use of a live registry like consul will then generated broken upstream services.
I cannot image a single usecase where this makes actual sense.
I would suggest, we either reimplement
consul_services
to include only health services or we introduceconsul_services_healthy
as an additional variable for that.Pseudo code would be somewaht like
what are your thoughts on this?
The text was updated successfully, but these errors were encountered: