PV and PVC Deletion in Kubernetes and remains stuck in terminating state

First we need to note that :
When you need to delete both PV, PVC then you must start from PVC and then go for PV.

In case mistakenly a PV is deleted first then it goes in terminating state as shown below:
Deleted the pv mistakenly

Output : See the higlighted one

Enlisting the desired PVC for which the PV we have deleted as highlighted

Now if we delete that particular PVC so it will also go into terminating state as shown below

After deletion it also goes in terminating state.

Work Around

Edit the particular PVC like as shown

kubectl edit pvc < pvc name>

Remove that particular line just as highlighted below:

Once Edit is done that Terminiating state is no more there and PVC AND PV completely deleted.👏

Feel Free to query : Click Here

By: Ibrar Aziz (Cloud Enthusiast)

https://ibraraziz-cloud.blogspot.com/

https://www.linkedin.com/in/ibraraziz/

Comments

Managing AI Workloads in Kubernetes and OpenShift with Modern GPUs [H100/H200 Nvidia]

AI workloads demand significant computational resources, especially for training large models or performing real-time inference. Modern GPUs like NVIDIA's H100 and H200 are designed to handle these demands effectively, but maximizing their utilization requires careful management. This article explores strategies for managing AI workloads in Kubernetes and OpenShift with GPUs, focusing on features like MIG (Multi-Instance GPU), time slicing, MPS (Multi-Process Service), and vGPU (Virtual GPU). Practical examples are included to make these concepts approachable and actionable. 1. Why GPUs for AI Workloads? GPUs are ideal for AI workloads due to their massive parallelism and ability to perform complex computations faster than CPUs. However, these resources are expensive, so efficient utilization is crucial. Modern GPUs like NVIDIA H100/H200 come with features like: MIG (Multi-Instance GPU): Partitioning a single GPU into smaller instances. Time slicing: Efficiently sharing GPU res...

What's New in Red Hat OpenShift 4.17

What's New in Red Hat OpenShift 4.17 Release Overview: · Kubernetes Version: OpenShift 4.17 is based on Kubernetes 1.30, bringing enhancements and new capabilities. Notable Beta Features: 1. User Namespaces in Pods: Enhances security by allowing pods to run with distinct user IDs while mapping to different IDs on the host. 2. Structured Authentication Configuration: Provides a more organized approach to managing authentication settings. 3. Node Memory Swap Support: Introduces support for memory swapping on nodes, enhancing resource management. 4. LoadBalancer Behavior Awareness: Kubernetes can now better understand and manage LoadBalancer behaviors. 5. CRD Validation Enhancements: Improves Custom Resource Definition (CRD) validation processes. Stable Features: 1. Pod Scheduling Readiness: Ensures that...

Choosing the Right OpenShift Service: Service Mesh, Submariner, or Service Interconnect?

In today’s digital world, businesses rely more and more on interconnected applications and services to operate effectively. This means integrating software and data across different environments is essential. However, achieving smooth connectivity can be tough because different application designs and the mix of on-premises and cloud systems often lead to inconsistencies. These issues require careful management to ensure everything runs well, risks are managed effectively, teams have the right skills, and security measures are strong. This article looks at three Red Hat technologies—Red Hat OpenShift Service Mesh and Red Hat Service Interconnect, as well as Submariner—in simple terms. It aims to help you decide which solution is best for your needs. OPENSHIFT Feature Service Mesh (Istio) Service Interconnect Submariner Purpose Manages service-to-service communication within a single cluster. Enables ...

Ibrar Aziz -Technology Enthusiast

Search This Blog