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
The current agent approach would be challenging for large repositories due to the time to clone. Can we create a mechanism for caching the repo within the cluster so that jobs using that repository will start more quickly?
Check solutions in the existing k8s ecosystem
The text was updated successfully, but these errors were encountered:
The current agent approach would be challenging for large repositories due to the time to clone. Can we create a mechanism for caching the repo within the cluster so that jobs using that repository will start more quickly?
Check solutions in the existing k8s ecosystem
The text was updated successfully, but these errors were encountered: