-
Notifications
You must be signed in to change notification settings - Fork 17
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
I want to run a RabbitMQ cluster reliably on K8s - What should I consider ? #13
Comments
After a summer break from TGIR, it was nice to come back to #13 from @omarelasfar and focus on helpful & practical advice in this new episode. While I may not be able to tick off all the issues raised, the list in this episode's README is more than decent. Signed-off-by: Gerhard Lazu <[email protected]>
Hi @omarelasfar, It was a nice surprise to find this here today, thanks for taking the time. The CommitStrip is most appreciated & fitting 😄 How does the proposed list of topics in #14 look like to you? |
Thanks @gerhard For looking into this proposal. It took me a while searching for the most fitting CommitStrip, more time invested in the CommitStrip than the actual ticket creation :). Episode 06 does cover the majority of what Ifs I had in mind (Cannot see in all listed items a dedicated line item for stack sets configs /liveness and readiness probs etc). But the list is inclusive enough to provide very practical guidance on running a cluster. I think it closes this ticket and I can open a new one in case something else pops up while running a cluster. |
And that's how I can tell apart those that are after quick help vs committed learning (pun intended) 🙂
Good spot! I've bumped the last item and introduced readiness & liveness probes as a first topic to tackle.
I like your thinking 😉 |
I had to push this back by a few days, ETA last day in September. Have a great weekend! |
Following up on this amazing first ticket for the topic.
RabbitMQ runs also in a cluster. Kubernetes pods are unpredictable, What should take care of while operating a RabbitMQ cluster on K8s.
The text was updated successfully, but these errors were encountered: