-
Notifications
You must be signed in to change notification settings - Fork 272
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
Problem with overriding statefulset readiness probe #1698
Comments
While allowing the probe to be overriden is something we can consider, can you explain what you are trying to accomplish here? Why do you expect |
@mkuratczyk, we are facing the same issue with overriding
|
I've temporary fixed error by commenting readinessProbe as follows:
Cluster has started without errors
But as always, temporary solution might be a permanent one 🥇 |
We are not against the idea, so PRs welcome. This is an open source project, you don't have to wait for us to get around to implementing this. |
This issue has been marked as stale due to 60 days of inactivity. Stale issues will be closed after a further 30 days of inactivity; please remove the stale label in order to prevent this occurring. |
Describe the bug
Overriding stateful set readiness probe from tcpSocket to exec keeps tcpSocket in its config.
To Reproduce
kubectl apply -f cluster-test.yml
kubectl get statefulset rabbitmq-test-server -o yaml
statefulset did not override readiness probe but keeps both exec and tcpSocket configs as follows:
which results in error
patching stateful set is an option to fix but it is not ideal!, please help.
The text was updated successfully, but these errors were encountered: