Streamlined Kubernetes API endpoint calling timeouts #503
No reviewers
Labels
No labels
API
Billing
UI/UX
dependencies
bug
change
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
servala/servala-portal!503
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "k8s-timeout-tweaks"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A slow or broken K8s endpoint (especially through a SOCKS5 proxy) could hang a request past gunicorn's 30s worker timeout, causing SystemExit:1 aborts and 500s. Config-level connect_timeout/read_timeout on kubernetes.client.Configuration weren't reliably honored through the SOCKS path because PySocks uses its own socket timeout sourced from urllib3's per-request Timeout.
Fix: Centralized timeout policy via an ApiClient subclass.
083991cbf4toc936cbfa45c936cbfa45to68ff9d5398WIP: improve overall k8s api connection handlingto Streamlined Kubernetes API endpoint calling timeoutsbbaec44aa251c080fc83