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
This improvement was requested in #6543. PVCs that have access mode "ReadWriteOnce" can't be accessed in parallel from pods running on different nodes, and in these cases it is appropriate to use the affinity assistant to schedule them to the same node. However, if a cluster operator allows usage of "ReadWriteMany" and "ReadOnlyMany" PVCs as well, these can be accessed from different nodes, and it's not necessary to use the affinity assistant. We should consider updating the coscheduling options "workspaces" and "pipelineruns" to take into account PVC access mode, to provide more optionality for clusters where both "ReadWriteOnce" and "ReadWriteMany" access modes are used.
The text was updated successfully, but these errors were encountered:
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
This improvement was requested in #6543. PVCs that have access mode "ReadWriteOnce" can't be accessed in parallel from pods running on different nodes, and in these cases it is appropriate to use the affinity assistant to schedule them to the same node. However, if a cluster operator allows usage of "ReadWriteMany" and "ReadOnlyMany" PVCs as well, these can be accessed from different nodes, and it's not necessary to use the affinity assistant. We should consider updating the coscheduling options "workspaces" and "pipelineruns" to take into account PVC access mode, to provide more optionality for clusters where both "ReadWriteOnce" and "ReadWriteMany" access modes are used.
The text was updated successfully, but these errors were encountered: