Currently rabbitmq takes almost a minute to start on slower machines. Other guys take seconds. As a result they come up first, try and fail to contact rabbitmq, and then crash. This means that the system takes longer than it needs to to come up due to the crash back-off state k8 goes into.
Is there a way to easily prevent clients from starting until rabbitmq has started?
In the end, k8 handles this, it just feels "ugly".
Currently rabbitmq takes almost a minute to start on slower machines. Other guys take seconds. As a result they come up first, try and fail to contact rabbitmq, and then crash. This means that the system takes longer than it needs to to come up due to the crash back-off state k8 goes into.
Is there a way to easily prevent clients from starting until rabbitmq has started?
In the end, k8 handles this, it just feels "ugly".