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.

Sign up for GitHub

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

Jump to bottom

HelmRelease Upgrade Timeout is likely too short #217

Closed
chrisseto opened this issue Sep 5, 2024 · 1 comment
Closed

HelmRelease Upgrade Timeout is likely too short #217

chrisseto opened this issue Sep 5, 2024 · 1 comment

Comments

@chrisseto
Copy link
Contributor

chrisseto commented Sep 5, 2024 •
edited by github-actions bot
Loading

As discussed/noted in this thread. The static upgrade timeout of 15 minutes is likely too short for production usage.

Before blindingly changing the timeout we should do some investigating to understand why upgrades take so long (This reportedly surfaces most frequently in clusters under heavy load).

The timeout (very likely) should scale linearly with the total number of nodes rather than being a static value.

See also:

JIRA Link: K8S-341
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chrisseto and others