-
Notifications
You must be signed in to change notification settings - Fork 805
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
Installation on GKE autopilot fails with hub pod in CrashLoopBackoff #3163
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
There are a few posts on https://discourse.jupyter.org/ about using GKE, try searching through that forum. If you're still stuck please post on that forum, and include enough information for someone to reproduce your problem from scratch. |
Hi there @vizeit 👋! I closed this issue because it was labelled as a support question. Please help us organize discussion by posting this on the https://discourse.jupyter.org/ forum. If it's your first time posting Our goal is to sustain a positive experience for both users and developers. We use GitHub issues for specific discussions related to changing a repository's content, and let the forum be where we can more generally help and inspire each other. Thanks you for being an active member of our community! ❤️ |
Bug description
Installation on GKE Autopilot fails with hub pod in CrashLoopBackoff with the log showing following error
api_request to the proxy failed with status code 599, retrying...
Expected behaviour
The installation should complete successfully
Actual behaviour
How to reproduce
Try to install on GKE Autopilot
Your personal set up
Full environment
Configuration
# jupyterhub_config.py
Logs
The text was updated successfully, but these errors were encountered: