Keep pipecd server data even when developer shut down pipecd or kind on local computer #6192
+55
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does:
.pipecd-data/
Why we need it:
Every time I execute
make stop/pipecd
, I also lost all the data that I have "worked hard" to create on my local pipecd server, then I have to create them all over again on next pipecd run. The root cause is: the mysql, minio, cache storage deployments got restart, and their data also lost.This PR is for mounting the local volume to storage data in kind cluster, so the data will be kept even when the mysql, minio, cache storage deployments are shut down. So when developer execute
make stop/pipecd
, ormake kind-down
or even restart her computer, she would still have all data available when he restart the local pipecd server.Which issue(s) this PR fixes:
Solve Item 3 in #6152
Does this PR introduce a user-facing change?: