k8s pvc扩容:pvc创建后扩容
k8s 创建 扩容 PVC
2023-09-14 09:01:49 时间
k8s pvc扩容:pvc创建后扩容
最开始的10g太小了,现在想扩容pv空间
1、kubernetes 1.11版本中开始支持pvc创建后的扩容
先查看storageclass是否配置了动态扩容,主要看storageclass是否存在allowVolumeExpansion字段
[root@192 ~]# kubectl get storageclass default -oyaml
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: default
parameters:
archiveOnDelete: "false"
provisioner: nfs-client-provisioner-default
reclaimPolicy: Delete
volumeBindingMode: Immediate
[root@192 ~]#
可以看到并没有allowVolumeExpansion,此时是不支持动态扩容的,可以扩一下测试看看
[root@192 ~]# kubectl edit pvc -n leijun-mysql comom-store-column-03-24
# Please edit the object below. Lines beginning with a '#' will be ignored,
# and an empty file will abort the edit. If an error occurs while saving this file will be
# reopened with the relevant failures.
#
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: comom-store-column-03-24
namespace: default
spec:
accessModes:
- ReadWriteMany
dataSource: null
resources:
requests:
storage: 50Gi
volumeName: pvc-24fc01a0-6d9b-11ea-9107-b8ca3a62236c
status:
accessModes:
- ReadWriteMany
capacity:
storage: 10Gi
phase: Bound
"/tmp/kubectl-edit-fkm33.yaml" 38L, 1180C written
error: persistentvolumeclaims "comom-store-column-03-24" could not be patched: persistentvolumeclaims "comom-store-column-03-24" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
You can run `kubectl replace -f /tmp/kubectl-edit-fkm33.yaml` to try this update again.
[root@192 ~]#
kubectl edit pvc -n leijun-mysql comom-store-column-03-24
修改storage 字段再保存,报错了,表示不支持动态扩容
2、给storageclass添加allowVolumeExpansion字段
[root@192 ~]# kubectl edit storageclass default
# Please edit the object below. Lines beginning with a '#' will be ignored,
# and an empty file will abort the edit. If an error occurs while saving this file will be
# reopened with the relevant failures.
#
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: default
parameters:
archiveOnDelete: "false"
provisioner: nfs-client-provisioner-default
reclaimPolicy: Delete
volumeBindingMode: Immediate
allowVolumeExpansion: true #增加该字段表示允许动态扩容
~
"/tmp/kubectl-edit-x0fyj.yaml" 24L, 738C written
storageclass.storage.k8s.io/default edited
[root@192 ~]#
3、再次修改pvc spec.resources.requests.storage字段
[root@192 ~]# kubectl edit pvc comom-store-column-03-24
spec:
accessModes:
- ReadWriteMany
dataSource: null
resources:
requests:
storage: 30Gi
volumeName: pvc-24fc01a0-6d9b-11ea-9107-b8ca3a62236c
status:
accessModes:
- ReadWriteMany
capacity:
storage: 10Gi
phase: Bound
"/tmp/kubectl-edit-mibh7.yaml" 38L, 1180C written
persistentvolumeclaim/comom-store-column-03-24 edited
[root@192 ~]#
相关文章
- Google、Azure、阿里云、RedHat…全球的 K8s 圈大佬聚在一起要聊啥?
- Centos7 k8s v1.5.2二进制部署安装-交付dubbo服务到k8s集群准备工作
- K8S Pod控制器:ReplicationController ReplicaSet Deployment三者的联系与区别
- k8s pvc扩容:pvc创建后扩容
- 【GO】K8s 管理系统项目12[API部分--Ingress]
- 【云原生 | Kubernetes 系列】war包部署Jenkins war包k8s部署
- k8s 创建私有docker仓库 登陆授权令牌的Secret
- 群晖 创建nfs 共享文件夹 k8s 使用
- k32.第十三章 K8s高级篇-中间件容器化及Helm (三)
- k10.第四章 K8s基础篇-基本概念 (一)
- y62.第三章 Kubernetes从入门到精通 -- k8s资源限制(三五)
- k8s 1.24.0版本使用nfs-provisioner4.0.0动态创建PV
- k8s-命令创建service
- 【博客594】k8s进行cpu绑核优化后,再配合NUMA 亲和性以进一步优化cpu性能
- 【 博客583】k8s常用集群运维操作命令汇总
- Kubernetes_部署_k8s的四种部署策略(滚动更新、重新创建、金丝雀部署、蓝绿部署)
- K8S故障排查指南:部分节点无法启动Pod资源-Pod处于ContainerCreating状态
- 【云原生】Presto/Trino on k8s 环境部署
- 【云原生】centos7搭建安装k8s集群 v1.25版本详细教程实战
- K8S 创建 Ingress