{"id":1007,"date":"2024-09-27T15:21:05","date_gmt":"2024-09-27T15:21:05","guid":{"rendered":"https:\/\/blog.ngocha.biz\/?p=1007"},"modified":"2024-09-27T15:21:05","modified_gmt":"2024-09-27T15:21:05","slug":"resize-volume-eks-cluster","status":"publish","type":"post","link":"https:\/\/blog.ngocha.biz\/?p=1007","title":{"rendered":"How to Resize Persistent Volumes in AWS EKS Cluster"},"content":{"rendered":"

In this blog, you will learn how to resize the persistent volume in AWS EKS cluster by using a custom storage class with the allowVolumeExpansion<\/code><\/strong> parameter enabled.<\/p>\n

Using Default StorageClass<\/h2>\n

In every EKS cluster<\/a>, there is default Storage class with allowVolumeExpansion<\/code><\/strong> false. Which means you cannot update a persistent volume with the default storage class.<\/p>\n

Lets look at the default storage class to understand more.<\/p>\n

Run the following command to get the default storageclass name.<\/p>\n

kubectl get sc<\/code><\/pre>\n
The name of my default storage class is given below.<\/p>\n
\"getting<\/figure>\n
As you can see in the default storage class, the allowVolumeExpansion<\/code><\/strong> parameter is set as false.<\/p>\n
If we try to resize the persistence volume, which uses the default storage class, we will get the below forbidden error.<\/p>\n
error: persistentvolumeclaims \"expandable-pvc\" could not be patched: persistentvolumeclaims \"expandable-pvc\" is forbidden: only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize\nYou can run `kubectl replace -f \/var\/folders\/w8\/zfm6dvnj5ng6cmpv61_nydh00000gn\/T\/kubectl-edit-57474951.yaml` to try this update again.<\/code><\/pre>\n
Using Custom StorageClass<\/h2>\n
Let’s try to expand a PVC that uses custom storageclass with allowVolumeExpansion<\/code><\/strong> parameter set as true.<\/p>\n
Step 1: Create Custom StorageClass<\/h3>\n
Now, let’s create a custom storage class and create the PVC with the custom storageclass.<\/p>\n
Create a YAML file sc.yaml<\/strong> and copy the below manifest file content<\/p>\n
apiVersion: storage.k8s.io\/v1\nkind: StorageClass\nmetadata:\n  name: expandable-sc\nprovisioner: kubernetes.io\/aws-ebs\nparameters:\n  type: gp2\nallowVolumeExpansion: true<\/code><\/pre>\n
You can see in the above manifest file, the allowVolumeExpansion<\/code><\/strong> is set as true.<\/p>\n
The EBS volume type is set to gp2<\/code><\/strong>, if you want to use other volume types refer to this guide<\/a>.<\/p>\n
Let’s create the PVC using the custom storageclass and try to expand the volume size.<\/p>\n
Run the following command to create the custom storageclass<\/p>\n
kubectl apply -f sc.yaml<\/code><\/pre>\n
Now, run the below command to check if the storageclass is created<\/p>\n
kubectl get sc<\/code><\/pre>\n
\"listing<\/figure>\n
The custom storageclass volumeBindingMode<\/code> is set as Immediate, which means the PVC will be created and bound with a PV immediately after it’s created.<\/p>\n
Step 2: Create PVC<\/h3>\n
Create a manifest file pvc.yaml<\/strong> and copy the below PVC manifest content<\/p>\n
apiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\n  name: expandable-pvc\nspec:\n  accessModes:\n    - ReadWriteOnce\n  volumeMode: Filesystem\n  resources:\n    requests:\n      storage: 1Gi\n  storageClassName: expandable-sc<\/code><\/pre>\n
You can see the storage requested is 1Gi<\/code><\/strong>. Run the following command to create a PVC<\/p>\n
kubectl apply -f pvc.yaml<\/code><\/pre>\n
Run the following command to check if the PVC is created.<\/p>\n
\"checking<\/figure>\n
As you can see, the PVC is in the bound state even without being claimed by a pod <\/a>because the custom storageclass we created has the volumeBindingMode<\/code><\/strong> as Immediate<\/code><\/strong>.<\/p>\n
Step 3: Deploy a Pod<\/h3>\n
Now, create a manifest file pod.yaml<\/strong> and copy the below pod deployment manifest content<\/p>\n
apiVersion: v1\nkind: Pod\nmetadata:\n  name: volume-test\nspec:\n  containers:\n  - name: volume-test\n    image: nginx\n    volumeMounts:\n    - name: expandable-storage\n      mountPath: \/data\n  volumes:\n  - name: expandable-storage\n    persistentVolumeClaim:\n      claimName: expandable-pvc<\/code><\/pre>\n
Run the following command to deploy the pod<\/p>\n
kubectl apply -f pod.yaml<\/code><\/pre>\n
Step 4: Expand the Volume Size<\/h3>\n
Now, run the following command to edit the PVC to expand the volume size.<\/p>\n
k edit pvc expandable-pvc<\/code><\/pre>\n
Then, change the storage request size to 2Gi<\/code><\/strong> as shown below<\/p>\n
\"editing<\/figure>\n
Save the changes and exit.<\/p>\n
Wait for some time, and the PV and PVC capacity will be increased, as shown below.<\/p>\n
\"checking<\/figure>\n
Now that the volume has been increased, it’s important to check if the filesystem’s size inside the pod has also increased.<\/p>\n
Run the following command to check whether the filesystem size is increased.<\/p>\n
kubectl exec -it volume-test -- df -h \/data<\/code><\/pre>\n
You can see the filesystem size has been increased as well.<\/p>\n
\"checking<\/figure>\n
Conclusion<\/h2>\n
In this blog, you have seen what happens if we change the volume size in the EKS cluster using the default storage class, which has allowVolumeExpansion<\/code><\/strong> parameter disabled.<\/p>\n
Also, you have learned how to expand a volume size using a custom storage class, which has allowVolumeExpansion<\/code><\/strong> parameter enabled.<\/p>\n
Also, resizing volume is one of the important topic in CKA certification<\/a>.<\/p>\n
\n
Ngu\u1ed3n:<\/strong> How to Resize Persistent Volumes in AWS EKS Cluster \u2014 DevOpsCube<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Source: https:\/\/devopscube.com\/resize-volume-eks-cluster\/<\/p>\n","protected":false},"author":1,"featured_media":1008,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1007","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops"],"_links":{"self":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts\/1007","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1007"}],"version-history":[{"count":0,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts\/1007\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/media\/1008"}],"wp:attachment":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1007"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1007"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1007"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}