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
Is your feature request related to a problem?
Currently devspace dependency cache is stored at ~/.devspace/dependencies, whereas the local devspace cache is stored at .devspace in the directory of the current devspace file.
This makes for a challenging user experience when re-building a local kind cluster, as the global dependency cache has to be cleared in order for dependency images to be built and loaded into the fresh kind cluster. Whenever I nuke and re-create a kind cluster, I constantly have todevspace reset dependencies which purges the global dependency cache in order to get things to work right on a fresh cluster install. This means the dependency cache I have for other repos also gets cleared.
Which solution do you suggest?
Move the dependency cache to be in-line with the .devspace directory, so that each project has its own dependency cache
Which alternative solutions exist?
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
Currently devspace dependency cache is stored at
~/.devspace/dependencies
, whereas the local devspace cache is stored at.devspace
in the directory of the current devspace file.This makes for a challenging user experience when re-building a local kind cluster, as the global dependency cache has to be cleared in order for dependency images to be built and loaded into the fresh kind cluster. Whenever I nuke and re-create a kind cluster, I constantly have to
devspace reset dependencies
which purges the global dependency cache in order to get things to work right on a fresh cluster install. This means the dependency cache I have for other repos also gets cleared.Which solution do you suggest?
Move the dependency cache to be in-line with the
.devspace
directory, so that each project has its own dependency cacheWhich alternative solutions exist?
Additional context
The text was updated successfully, but these errors were encountered: