Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

How the remote client simply waits for rabbitmq-server to be ready #4279

Closed
lizhifengones opened this issue Mar 16, 2022 · 1 comment
Closed

Comments

@lizhifengones
Copy link

I see that rmq has added a lot of cool health checks (rabbitmq/rabbitmq-management#844).

I am a rookie of rabbitmq. When I have some microservices in k8s that depend on rabbitmq, I will consider using init-container to wait for rabbitmq, but I have not found a good way.

@michaelklishin
Copy link
Member

I will convert this issue to a GitHub discussion. Currently GitHub will automatically close and lock the issue even though your question will be transferred and responded to elsewhere. This is to let you know that we do not intend to ignore this but this is how the current GitHub conversion mechanism makes it seem for the users :(

@rabbitmq rabbitmq locked and limited conversation to collaborators Mar 16, 2022
@michaelklishin michaelklishin converted this issue into discussion #4280 Mar 16, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants