简体   繁体   English

Kubernetes 持久卷声明 FileSystemResizePending

[英]Kubernetes Persistent Volume Claim FileSystemResizePending

i have a persistent volume claim for a kubernetes pod which shows the message "Waiting for user to (re-)start a pod to finish file system resize of volume on node."我有一个 kubernetes pod 的持久卷声明,它显示消息“等待用户(重新)启动一个 pod 以完成节点上卷的文件系统调整大小。” if i check it with 'kubectl describe pvc...'如果我用“kubectl describe pvc ...”检查它

The rezising itself worked which was done with terraform in our deployments but this message still shows up here and i'm not really sure how to get this fixed?在我们的部署中使用 terraform 完成了调整本身的工作,但此消息仍然显示在这里,我不确定如何解决这个问题? The pod was already restarted several times - i tried kubectl delete pod and scale it down with kubectl scale deployment. pod 已经重新启动了好几次——我尝试了 kubectl delete pod 并使用 kubectl scale 部署来缩小它。

Does anyone have an idea how to get rid of this message?有谁知道如何摆脱这个消息? screenshot截屏

There are few things to consider:有几件事情需要考虑:

  1. Instead of using the Terraform, try resizing the PVC by editing it manually.不要使用 Terraform,而是尝试通过手动编辑来调整 PVC 的大小。 After that wait for the underlying volume to be expanded by the storage provider and verify if the FileSystemResizePending condition is present by executing kubectl get pvc <pvc_name> -o yaml .之后,等待存储提供程序扩展底层卷,并通过执行kubectl get pvc <pvc_name> -o yaml验证是否存在FileSystemResizePending条件。 Than, make sure that all the associated pods are restarted so the whole process can be completed.然后,确保所有关联的 pod 都重新启动,以便完成整个过程。 Once file system resizing is done, the PVC will automatically be updated to reflect new size.文件系统大小调整完成后,PVC 将自动更新以反映新的大小。

  2. Make sure that your volume type is supported for expansion.确保您的卷类型支持扩展。 You can expand the following types of volumes:您可以扩展以下类型的卷:

  • gcePersistentDisk gcePersistentDisk

  • awsElasticBlockStore awsElasticBlockStore

  • Cinder煤渣

  • glusterfs glusterfs

  • rbd rbd

  • Azure File Azure 文件

  • Azure Disk Azure磁盘

  • Portworx波特沃克斯

  • FlexVolumes弹性卷

  • CSI CSI

  1. Check if in your StorageClass the allowVolumeExpansion field is set to true .检查您的StorageClass中的allowVolumeExpansion字段是否设置为true

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 MySQL 对 Kubernetes 的持久卷声明 - MySQL with Persistent Volume Claim on Kubernetes GCE Kubernetes:永久磁盘和永久卷声明 - GCE Kubernetes: Persistent disk and Persistent Volume claim 将新卷附加到持久卷声明 (Kubernetes) - Attaching New Volume to Persistent Volume Claim (Kubernetes) Kube.netes Persistent Volume Claim indefinitely in Pending State - Kubernetes Persistent Volume Claim Indefinitely in Pending State 通过 Kubernetes 作业和持久卷声明进行 Django 迁移 - Django migrations by Kubernetes Job and persistent Volume Claim Azure Kubernetes 服务 - 持久卷/持久卷声明更改权限 - Azure Kubernetes Service - Persistent Volume / Persistent Volume Claim change permissions 持久卷和持久卷声明在 kubernetes 中如何相互绑定 - How persistent volume and persistence volume claim bound each other in kubernetes 在dockerfile中创建一个没有Kubernetes中的持久卷(声明)的卷? - Creating a volume in a dockerfile without a persistent volume (claim) in Kubernetes? 在 kubernetes 中创建持久卷声明时不应用空终结器 - Null finalizers not applied when creating a Persistent Volume Claim in kubernetes 如何为kubernetes中的软件安装提供永久批量声明 - How to provision persistent volume claim for software install in kubernetes
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM