You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
I have created a template which uses a volume claim template. If the total claimed by running pods is at storage quota then new pods being attempted to run enter error state rather than pending state.
What you expected to happen:
If storage resources are unavailable then workflow should remain pending until resources are available.
How to reproduce it (as minimally and precisely as possible):
In a namespace with a quota of 10Gi of storage the error should start occuring after 5 have been submitted.
Checklist:
What happened:
I have created a template which uses a volume claim template. If the total claimed by running pods is at storage quota then new pods being attempted to run enter error state rather than pending state.
What you expected to happen:
If storage resources are unavailable then workflow should remain pending until resources are available.
How to reproduce it (as minimally and precisely as possible):
In a namespace with a quota of 10Gi of storage the error should start occuring after 5 have been submitted.
Use bash script to run this some number of times until you encounter the issue.
Anything else we need to know?:
I believe this issue also occurs when hitting PVC limits.
Environment:
Other debugging information (if applicable):
Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: