Скачать или смотреть How to Create a PVC/PV Backed by a Pre-existing EBS Volume in Kubernetes

Learn how to reuse your existing Amazon EBS volumes in Kubernetes by creating a PersistentVolume and PersistentVolumeClaim that reference them directly.
---
This video is based on the question https://stackoverflow.com/q/63615246/ asked by the user 'RubenLaguna' ( https://stackoverflow.com/u/90580/ ) and on the answer https://stackoverflow.com/a/63615247/ provided by the user 'RubenLaguna' ( https://stackoverflow.com/u/90580/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How can create a PVC/PV that backed by a pre-existing EBS volume?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Create a PVC/PV Backed by a Pre-existing EBS Volume in Kubernetes

In the world of Kubernetes, managing storage is a critical task, especially when it comes to handling persistent volumes. A common scenario is the accidental deletion of a PersistentVolumeClaim (PVC) or PersistentVolume (PV) that leads to the need to reconnect to a pre-existing Amazon Elastic Block Store (EBS) volume. This guide will guide you through the process of reconnecting your Kubernetes applications to an EBS volume that has been retained through a specific reclaim policy.

The Problem: Lost PVC/PV But Retained EBS Volume

You may find yourself in a situation where:

You created a PVC/PV that was linked to an EBS volume.

The PVC/PV was accidentally deleted, but you want to retain the data stored on the EBS volume.

Your EBS volume still exists because its reclaimPolicy is set to Retain.

Example Setup

Assuming you initially created a persistent volume like this:

[[See Video to Reveal this Text or Code Snippet]]

And a corresponding PersistentVolumeClaim:

[[See Video to Reveal this Text or Code Snippet]]

Goal

Now, your objective is to recreate a PVC and PV that links to this retained EBS volume identified by the volume ID, for example, aws://eu-west-1/vol-xxxxx.

The Solution: Adopting the Existing EBS Volume

To "adopt" your existing EBS volume into a new PVC and PV setup, you can follow these steps:

Step 1: Create a PersistentVolume

Define a PersistentVolume with a unique name (e.g., vol-imported-prometheus-server) and set its volumeID to your existing EBS volume:

[[See Video to Reveal this Text or Code Snippet]]

Important Note: Specifying the volumeID prevents Kubernetes from trying to dynamically provision a new EBS volume.

Step 2: Create a PersistentVolumeClaim

Define a PersistentVolumeClaim that references the PersistentVolume created in the previous step:

[[See Video to Reveal this Text or Code Snippet]]

Important Note: By specifying volumeName, you ensure that Kubernetes binds the PVC to the existing PV rather than dynamically provisioning a new one.

Step 3: Apply Your Configurations

Once you’ve created the YAML files, you can deploy them using the kubectl apply command:

[[See Video to Reveal this Text or Code Snippet]]

After running this command, confirm that your PVC and PV are bound correctly by checking their status:

[[See Video to Reveal this Text or Code Snippet]]

You should see output indicating that the PersistentVolume is bound to the PersistentVolumeClaim.

Step 4: Use the PVC in Your Application

Finally, you can use the created PVC in your Helm chart or Kubernetes deployment:

[[See Video to Reveal this Text or Code Snippet]]

Here, replace imported-prometheus-server with the name of the PVC you just created.

Conclusion

By following these steps, you can easily adopt an existing EBS volume into a new Kubernetes configuration, ensuring that your application can access the retained data even after the loss of the PVC or PV. This process allows you to make the best use of your existing resources without losing crucial data.

Now you have the knowledge to efficiently manage your persistent storage even in challenging situations! Happy Kubernetes managing!