- Plan Your Installation
- Install Tanzu Community Edition
- Microsoft Azure
- Headless Installation
- AWS Account Reference
- AWS Workload Cluster Template
- vSphere Account Reference
- vSphere Workload Cluster Template
- Azure Account Reference
- Azure Workload Cluster Template
- Docker-based Clusters on Windows
- Work with Packages
Local Path Storage
- Run Conformance Tests
- Scale Management Cluster
- Delete Management Cluster
- Delete Workload Cluster
- Uninstall the Tanzu CLI
- Upgrade kapp-controller version
- Secure automated ingress on AWS
- Opinionated installation package
- Monitoring with Prometheus and Grafana on vSphere
- Monitoring with Prometheus and Grafana on Docker
- LDAP Integration on vSphere and NSX-ALB
- Package Creation, Step by Step
- Troubleshoot Clusters
- File a Bug or Feature
- Our Triage Process
- Getting Support
Local Path Storage - v0.0.20 ¶
This package provides local path node storage and primarily supports RWO AccessMode. It utilizes the Kubernetes Local Persistent Volume feature and in Tanzu Community Edition, it is primarily intended for use with Docker, although it will work with any infrastructure provider or package where persistent storage is needed.
This package also provides a
If there is no
StorageClass already installed on the cluster,
StorageClass provided in this package will automatically be made the default.
storageclass.kubernetes.io/is-default-class may need to be modified.
The local-path-storage binds to a single host node and is not intended to dynamically change hosts. Therefore, a PVC can only be used by the node that creates it. This can lead to unintended data loss when scaling or when pods roll from one node to another. Further, it can make scheduling difficult since applications are “tied” to the node that created it’s PV.
Further, local-path-storage does not enforce capacity limitations and may possibly overwhelem the local node’s disc capacity.
See the local-path-storage GitHub for further documentation and configuration options.
|Required||The namespace to deploy the local-path-storage pods|
Note: The local path storage provides a config map that may be modified after installation.
This includes a
config.json that can be used to further configure the storage provider.
teardown scripts are defined in the config map and are used in the lifecycle of persistent volumes.
The local-path-storage pods will dynamically reload the config map upon configuration without need to reapply the deployment.
Usage Examples ¶
A StorageClass is required in order to use PVCs and store data (which is necessary for services like Prometheus). The local-path-storage provider enables local Docker clusters to store data locally. Using a local PVC with Docker lets a developer work quickly on their own workstation with Docker.
A local storage provider may also be used in special cases for caching, sharding data in distributed datastores, and other node failure tollerant storage models. Note that local storage providers are generally not suitiable for most production use cases.