Maintain Remote copies of Local PV - a lesson for rainy days

As we get lured into its performance, we have to watch out for some of the common disasters that can hit really hard - if left unchecked. We will list the different challenges or shortcomings of the Local PV along with the available Open Source solutions and tools to address them.
For example, data protection can be achieved via Velero and Restic.
This talk will help all the kubernetes users who have been using the local PV or OpenEBS local PV in production for better performance but are worried about long term data management. In the talk, we will share our experience with local PV in production, as well as measures we took to ensure nothing is lost during worst-case scenarios.

Transcript

1. Maintain Remote copies of Local PV - a lesson for rainy days Jeffry Molanus CTO, MayaData Harshvardhan Karn Software Engineer, MayaData Visit us at KubeCon Booth SE23
2. Join us on Monday
3. www.mayadata.io
4. • Policies • Preparation • Metrics Why LocalPV? A local persistent volume represents a local disk directly-attached to a single Kubernetes Node.
5. Rainy Days // a time of need or trouble • Data loss • Data corruption
6. OpenEBS and LocalPV • Local PVs are provisioned dynamically by OpenEBS Local PV provisioner. When the Local PV is provisioned with the default StorageClass with storage-type as : ◦ hostpath, the default BasePath is created dynamically on the node and mapped to the Local PV. ◦ device, one of the matching BlockDevice on the node is claimed and mapped to the Local PV. • Dedicated management of Block Device for LocalPV using OpenEBS NDM • Guarantees Pod and local PV to be scheduled on same node using node selector.
7. Remote Copies Using Velero Restic we can backup and restore the data, when needed for rainy days
9. Thank You @JeffryMolanus @harshvkarn @chandankr41