Skip to content

Change readinessProbe to tcpSocket #413

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.

Sign up for GitHub

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

Jump to bottom
Closed
mkuratczyk opened this issue Oct 27, 2020 · 1 comment · Fixed by #410
Closed

Change readinessProbe to tcpSocket #413

mkuratczyk opened this issue Oct 27, 2020 · 1 comment · Fixed by #410
Milestone
GA

Comments

@mkuratczyk
Copy link
Collaborator

As we learned in #409, rabbitmqcli-based readinessProbe is not reliable in some cases. Let's switch to a TCP-based probe like this:

        readinessProbe:
          tcpSocket:
            port: amqp
          initialDelaySeconds: 10
          periodSeconds: 10
          timeoutSeconds: 5
          successThreshold: 1
          failureThreshold: 3
@mkuratczyk mkuratczyk changed the title Change readinessProbe to be TCP-based Change readinessProbe to tcpSocket Oct 27, 2020
@mkuratczyk mkuratczyk added this to the GA milestone Oct 27, 2020
@mkuratczyk mkuratczyk linked a pull request Oct 27, 2020 that will close this issue
Use a tcp readiness probe instead of cli command #410
Merged
@mkuratczyk
Copy link
Collaborator Author

Duplicate of #410

@mkuratczyk mkuratczyk marked this as a duplicate of #410 Oct 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
GA
Development

Successfully merging a pull request may close this issue.

Use a tcp readiness probe instead of cli command rabbitmq/cluster-operator
1 participant
@mkuratczyk