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
We need a PVC only when caching is enabled, but for normal Kaniko build and push we can initialize the tar.gz in an init-container and then push it to the registry via the Kaniko pod (with data shared using a node local directory volume).
We can also disable image caching by default (caching is a simple but problematic piece, don't really know why). When caching is enabled we can mount the PV for the cache only.
I've started working on implementing the init container strategy. It's a bit more involved than I anticipated originally as it requires disentangling the scheduling logic from the build logic, and impacts the Build API, but I think it's worth the effort and it will ease supporting Tekton as build strategy eventually (#682).
We need a PVC only when caching is enabled, but for normal Kaniko build and push we can initialize the tar.gz in an init-container and then push it to the registry via the Kaniko pod (with data shared using a node local directory volume).
We can also disable image caching by default (caching is a simple but problematic piece, don't really know why). When caching is enabled we can mount the PV for the cache only.
wdyt @astefanutti ?
The text was updated successfully, but these errors were encountered: