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
I encountered the problem while interacting with the server (Backend)
What browsers are you seeing the problem on?
Chrome
Current behaviour
I have created kubernetes resources to host planka on my local k8s. I have mounted 2 volume for /app/public and /app/private. Volumes are mounted with right security group 1000 which node uses. The problem is when i delete the pod of server deployment creates a new pod. However new pod deletes all files in PV which is attached via PVC. I built my own images by using Dockerfile in the project. Do you know what could be the problem?
Desired behaviour
When a new pod is created and older pod is dead it should contain the background images and attachments.
Steps to reproduce
Built docker image
Create k8s deployment and pvc's
Configure a project and set project background image
Kill the pod and let the deployment create a new one
Background images will be gone.
Other information
No response
The text was updated successfully, but these errors were encountered:
Where is the problem occurring?
I encountered the problem while interacting with the server (Backend)
What browsers are you seeing the problem on?
Chrome
Current behaviour
I have created kubernetes resources to host planka on my local k8s. I have mounted 2 volume for
/app/public
and/app/private.
Volumes are mounted with right security group 1000 which node uses. The problem is when i delete the pod of server deployment creates a new pod. However new pod deletes all files in PV which is attached via PVC. I built my own images by using Dockerfile in the project. Do you know what could be the problem?Desired behaviour
When a new pod is created and older pod is dead it should contain the background images and attachments.
Steps to reproduce
Other information
No response
The text was updated successfully, but these errors were encountered: