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
In the Alpha, we support container persistence via hostpath mapping (which translates to a docker bind mount), which is rarely used in Kubernetes deployments. What is more common is PV's and PVC's coming from a storage class.
To provide standardised support for manifests that expect a PVC, we should emulate a default storage class (docker), make it the default, and then translate PVC's to Docker named volumes, akin to "docker volume create"
The text was updated successfully, but these errors were encountered:
ncresswell
changed the title
Support for emulation Persistent Volumes
Support for emulation of Persistent Volumes via PVCs
Aug 21, 2023
In the Alpha, we support container persistence via hostpath mapping (which translates to a docker bind mount), which is rarely used in Kubernetes deployments. What is more common is PV's and PVC's coming from a storage class.
To provide standardised support for manifests that expect a PVC, we should emulate a default storage class (docker), make it the default, and then translate PVC's to Docker named volumes, akin to "docker volume create"
The text was updated successfully, but these errors were encountered: