26676/create-volume-kubernetes-that-won-get-destroyed-even-the-pods
I have a docker image that when created should check if the volume is empty, in case it should initialize it with some data. This saved data must remain available for other pods with the same or different image.
What do you recommend me to do?
You can use the writemany which should alleviate a deadlock.
apiVersion: v1 kind: PersistentVolume metadata: name: shared-volume spec: capacity: storage: 1Gi volumeMode: Filesystem accessModes: - ReadWriteMany persistentVolumeReclaimPolicy: Retain storageClassName: "" mountOptions: - hard - nfsvers=4.1 nfs: path: /tmp server: 172.17.0.2
Persistent Volumes
if you need to do this is ...READ MORE
You get this error when your pod ...READ MORE
Fabric8's Kubernetes Client is using a generated ...READ MORE
When a node is tainted, the pods ...READ MORE
Hey @nmentityvibes, you seem to be using ...READ MORE
Try using ingress itself in this manner except ...READ MORE
It can work if you try to put ...READ MORE
When you use docker-compose down, all the ...READ MORE
You can define a health check in ...READ MORE
I had a similar issue, but mine ...READ MORE
OR
At least 1 upper-case and 1 lower-case letter
Minimum 8 characters and Maximum 50 characters
Already have an account? Sign in.