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
Can somebody elaborate why there is now (v2.3.0) a use for persistent volumes for registry, chartmuseum, jobservice, redis and trivy?
It seems because of the size they are used for caching?
We are hosting harbor in aws eks, so without readwritemany we will need to switch to efs which is way slower than ebs. Will the performance of efs be sufficient for the usecase of the persistent volumes?
Or does somebody know an alternative solution where pods are not bound to one availability zone?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Can somebody elaborate why there is now (v2.3.0) a use for persistent volumes for registry, chartmuseum, jobservice, redis and trivy?
It seems because of the size they are used for caching?
We are hosting harbor in aws eks, so without readwritemany we will need to switch to efs which is way slower than ebs. Will the performance of efs be sufficient for the usecase of the persistent volumes?
Or does somebody know an alternative solution where pods are not bound to one availability zone?
Beta Was this translation helpful? Give feedback.
All reactions