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

Velero pod should have 512Mi for the memory limit #231

Closed
dsu-igeek opened this issue Mar 9, 2021 · 0 comments · Fixed by #232
Closed

Velero pod should have 512Mi for the memory limit #231

dsu-igeek opened this issue Mar 9, 2021 · 0 comments · Fixed by #232
Assignees
@jenting

Comments

@dsu-igeek
Copy link

The limit for the Velero pod was bumped in release 1.5.3 from 256Mi to 512Mi due to crashes in the Azure plug-in with the smaller limit (vmware-tanzu/velero#3234). The Helm charts appears to be installing with the old limit (#168)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jenting jenting

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[velero] Sets default resource requests and limits jenting/vmware-tanzu-helm-charts
2 participants
@dsu-igeek @jenting