---------------------- You're right to be concerned about the future of persistent volumes with Garden. Based on the knowledge sources, there are some important changes coming in Garden 0.14 that affect how you should handle persistent data. ## Current Status and Future Direction The

persistentvolumeclaim

Deploy action type is being deprecated and will be removed in Garden 0.14. Additionally, volume container action references (the ability to reference

persistentvolumeclaim

actions from

container

actions) will also be removed in 0.14 [Deprecations and updating to Cedar](). ## Recommended Approach The recommended approach is to switch to using the

kubernetes

Deploy action type instead of the

container

action type when you need persistent volume claims. This is explicitly stated in the documentation: > "Use the

kubernetes

action type instead of the

container

action type if you need persistent volume claims or mount configmaps." [container Deploy Configuration Keys]() The

container

Deploy action type itself is also not recommended for production use. The documentation states: > "The

container

Deploy action type can be useful for getting started quickly but has several limitations and is not suitable for production. Instead we encourage users to use the

kubernetes

or

helm

types which are a lot more flexible." [K8s-plugins Actions]() ## How to Implement Persistent Storage For implementing persistent storage with the

kubernetes

action type, you should:

1. Create Kubernetes manifests for your PersistentVolumeClaims 2. Use the

kubernetes

Deploy action type to deploy these manifests 3. Reference these resources in your pod specifications The documentation refers to the [official Kubernetes documentation on configuring persistent volume storage]() for more details on how to implement this. There's also an ongoing discussion about potentially creating a new

kubernetes-container

action type that would combine the simplicity of the

container

type with more Kubernetes-specific capabilities, but this is still in the feature request stage [Github Issue: kubernetes-container Deploy action](). ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted