-
Notifications
You must be signed in to change notification settings - Fork 107
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
[FEATURE REQUEST] RabbitMQ needs to be highly available #1486
Comments
May be related and resolved similat to #1485 |
Looks like. Added dependency. |
Added section "More context is provided also in duplicate task #1485" to issue description. |
Hello Team, I was looking into this issue and wondering is it still something that is to be addressed? In that case what is expected to be done for it. |
#1455 is almost completed which would make this possible. If there is a need for it we can consider it. |
Adding comment from #1485 so we can close that one: Describe the bug To Reproduce Create Epiphany with RabbitMQ cluster on top of K8s Config files OS (please complete the following information): OS: [e.g. RHEL7] Suggestion from creator So in the StatefulSet configuration, in addition to this: mountPath: /etc/rabbitmq configMap:
add something like this (dependent on storage provider): name: rabbitmq-data metadata: |
We need to check this with outstanding pull #3122. @Harshini097t could you check if this is what you are working on? |
Not going todo anymore feature requests for Epiphany. |
Is your feature request related to a problem? Please describe.
When RabbitMQ is deployed as pods inside the Kubernetes cluster teh application needs RMQ to be highly available and not lose configuration or data when pods are moved, or VMs restarted, or cluster restored for backup/restore or DR activities.
Describe the solution you'd like
RabbitMQ clustered and replicated.
Describe alternatives you've considered
None
Additional context
Teams request, EP-112
More context from duplicate issue #1485 in comments below.
DoD checklist
The text was updated successfully, but these errors were encountered: