Allow Hetzner Volume to be reused by a different node/pod when another pod is terminating about terraform-hcloud-kube-hetzner HOT 4 CLOSED

Hi, sorry but this sounds like an issue of your mysql deployment.
Kind of sure this is outside of the scope of this project.

from terraform-hcloud-kube-hetzner.

I don't think this is a MySQL issue, the question about volumes is platform agnostic.

However, I can understand if this is not supported or recommended, if that is the case then I would like to hear it :)

from terraform-hcloud-kube-hetzner.

Hey, what I mean Hetzner Volume (hetzner-csi) does not support multi attach.
from https://github.com/hetznercloud/csi-driver
This is a [Container Storage Interface](https://github.com/container-storage-interface/spec) driver for Hetzner Cloud enabling you to use ReadWriteOnce Volumes within
So it is not a problem this project can fix.
I have no idea why the old mysql pod does not release the PV(c) when crashed/shutdown.
We have the hetzner volume in an other k8s cluster running in production, and they are running fine, e.g. delete pod, it gets recreated and starts up without problems.
Since you did not share more details like the mysql manifest yml, I can only speculate... maybe you do not have set valid resource limits for the mysql/Neo4J deployment.
So the memory spike kills the node, when the mysql pod should be killed in this case and this would release the PVC and restart should work.
bye

from terraform-hcloud-kube-hetzner.

Folks, just use the hcloud cli to detatch the volume the. reattach it to the correct node.

from terraform-hcloud-kube-hetzner.