Skip to content
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

Enable hub livenessProbe by default and relax hub/proxy probes #1941

Conversation

consideRatio
Copy link
Member

This PR closes #1936 and stems from a deliberations in #1732 that I suggest we close when we have added a startupProbe as suggested in an action point in #1732 (comment).

The actual changes are:

  1. Enable hub's livenessProbe by default.
  2. Make hub's livenessProbe start after 5 minutes (from 3), and trigger a pod restart after >5 minutes without any response (from >30s).
  3. Make hub's readinessProbe very relaxed so it won't fail before the hub's livenessProbe or generally at all, because it would not serve a purpose to have a non-ready hub pod as it doesn't support being run in parallel with another pod.
  4. Make proxy's readinessProbe be very relaxed for the same reasons at the hub pod.

@manics manics merged commit 8e7b699 into jupyterhub:master Dec 12, 2020
consideRatio pushed a commit to jupyterhub/helm-chart that referenced this pull request Dec 12, 2020
jupyterhub/zero-to-jupyterhub-k8s#1941 Merge pull request #1941 from consideRatio/pr/tweak-liveness-readiness-probes-settings-to-be-less-strict
@consideRatio
Copy link
Member Author

Wieee thanks for your help @manics!

@meeseeksmachine
Copy link

This pull request has been mentioned on Jupyter Community Forum. There might be relevant details there:

https://discourse.jupyter.org/t/jupyterhub-helm-chart-0-11-0-released/7521/1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

hub pod's readinessProbe too strict
3 participants