Could not restart piped after reboot local k8s cluster (minikube)

[mehboobpatel]

Hello Devs,

I am starting with pipecd i followed quickstart documentation and created the piped deployment in my local minikube but when i restarted my system and started minikube again the piped deployment was failing if the control pane remains persistent than why not the piped deployment as i have to again do the process of creation s/piped.yaml|
sed -e 's/<YOUR_PIPED_ID>/66ed2/g'
-e 's/<YOUR_PIPED_KEY_DATA>/azRjYW9yNzFvMXVrNHmV6djNwbXlnNzk=/g' |
kubectl apply -n pipecd -f -

[t-kikuc]

@mehboobpatel

Hi, thank you for reporting.
Would you please describe in the following format so that we can easily understand your situation? (Bug Report template)

**What happened**:

**What you expected to happen**:

**How to reproduce it**:

**Environment**:
- `piped` version:
- `control-plane` version:
- Others:

[khanhtc1202]

Hi @mehboobpatel, If you can inspect the piped pod log (using kubectl logs or similar tools), maybe we can have more information to understand what's actually going on.

For now, my only guess is, since you're using quickstart installation mode, all of the pipecd control plane components (including the datastore) are just the containers running in minikube cluster. This means after you restart those containers, the registered information for the piped (ID and access key) is invalid. Via the control plane UI, you can check whether the registered piped is still valid or not by visiting the setting/piped page.

You have to:

• Re-register for another piped from the control plane UI (ref: https://pipecd.dev/docs-v0.50.x/quickstart/#12-installing-piped)
• Or update the datastore container to persist the data to your host.

Please note that this instruction is just for Quickstart. We think that not everyone wants to persist in the datastore to the host, so we didn't update the Quickstart manifest anyway.

[mehboobpatel]

<---here is the logs , you are right this point is correct This means after you restart those containers, the registered information for the piped (ID and access key) is invalid. Via the control plane UI, you can check whether the registered piped is still valid or not by visiting the setting/piped page. <-- but dont you think that it would be better if the piped deployment persists by default like the developer doesnt have to update the datastore container to persist the data to your host.

[khanhtc1202]

@mehboobpatel it's a fair question 🙂
What is your plan to make that possible? Last time we thought about that, there were only two approaches:

• Persist the datastore to the host (ref: https://github.com/pipe-cd/pipecd/blob/master/manifests/pipecd/templates/deployment.yaml#L357)
• Make these data configurable like project info (ref: https://github.com/pipe-cd/pipecd/blob/master/quickstart/control-plane-values.yaml#L22-L26)

The (2) approach is quite difficult, and I'm not yet checking approach (1) carefully. We need to test each environment carefully to support different cluster platforms (minikube, docker4mac, kind, etc.). As I mentioned, not everyone wants to persist data on their host. If you have any better idea to resolve this, we can discuss it here :)

On the other hand, this is a quickstart. If you want to set up an environment for dev, I prefer to follow this contribution guideline instead. It's also preferred to restart the preparation process each time you change the code (of the controlplane). wdyt?