Connection Pooling for Connection to Kubernetes #348
Labels
No labels
API
Billing
UI/UX
dependencies
bug
change
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
servala/servala-portal#348
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Stories
As a user, I want to have fast responses when navigating to pages with Kubernetes API calls
Implementation Notes
We currently don't pool connections to the Kubernetes API, which slows down API requests quite a lot. Implement connection pooling to reuse connections for subsequent Kubernetes API calls.
Suggestion from Claud Code: