Itna achhe se koi nahi samajh payega aur itne details pe koi nahi bata payega…aut ek baat apka bolna aur samjhana bahut bahut achha hai mam….Thank you so much 😊😊
Hi. Could you please let me know which kubeadm version u r working on. I m still struggling with this. Kubeadm v1.29 on ec2. I get issue like "rpc error : could not provision volume. Context deadline exceeded". Any help would be very nice
This error can occur due to various reasons. Firstly, ensure your EC2 instances have the necessary permissions to create EBS volumes. Additionally, check your network connectivity and DNS resolution, as timeouts can occur if the Kubernetes nodes can't communicate properly. If the issue persists, providing more details about your setup would help diagnose the problem further.
@@DevOpsProI have added role to the IAM user with ec2fullaccess. Other than this not added any role. If any other role needs to be added kindly suggest me please
Hi Riya, You have created storage for centos, can you please create a video where a deployment 2 pods will create and an another multi pod will create in statefulset which consumed the ebs volume, I.e deployment + statefulset will communicate together
Hello, I followed all the same steps in my EKS setup but still my pod and pvc are showing me in pending state please suggest me to solve this issue.. BTW your explaining the concept with your awesome presentations are very helpful to understand the concepts
Mam, i created my cluster in eks.. It already default storage class present. So i am not creating storage class. I have the name of sc in pvc. And I follow your steps but my pvc and pod still in Pending state. Kindly help.
Please ensure that the PV you intend to use is available and configured correctly with matching capacity and access modes as specified in your PVC. Also check your PVC's storage class name and ensure it matches the one in your EKS cluster. If the problem persists, feel free to provide more details with us.
Hey Thanks for the tutorial....I have 1 question: The example you've shown is of cloud . what if we use nfs or we deployed k8s on Oracle Cloud . How the storage class file will look like?
For NFS, the storage class would reference an NFS provisioner, pointing to your NFS server and export path. For Oracle Cloud, you'd use a storage class configured for Oracle’s block storage, specifying the volume type, file system, and other Oracle-specific parameters. The setup will vary based on the storage type and cloud environment, but the basic structure remains similar.
Hi Mam, I hope this message finds you well. I had doubts regarding the volume provisioning, while creating the PVC. Basically, is it Bounded when we created the pod while specifying the claim name, or it took it's time to get bound ?
is it because of the VolumeBindingMode, that has been set to "WaitForFirstConsumer" ? Because the Pod was created, it immediately Bound the PVC and created the PV ( the EBS volume in AWS )
Yes, you’re correct-when VolumeBindingMode is set to WaitForFirstConsumer, the PVC gets bound to a PV only when a pod that uses it is scheduled. This ensures the volume is provisioned in the same zone as the pod. That’s why when you created the pod, the PVC immediately got bound and the EBS volume was created in AWS. It’s all about optimizing resource allocation. Hope this clears up your doubt!
If we create one more pod with different application, can we make use of the same storage class to provision another dynamic pv or how it should be processed.
Yes, you can use the same storage class to provision another dynamic PV for a different pod. Just create a new PersistentVolumeClaim (PVC) with the same storage class, and it will automatically provision a new PV for the new pod.
Not working, did exactly the steps mentioned, but volume mount failed... Can u plzz make a complete video on how to self managed cluster on ec2 including pv, pvs storage classs... I spent 3 days but didn't work... But thumps for clear explanation 👍
Can we take readWriteMany in access mode in pvc in ebs? Because I tried but it was not happening. Can you please make a video of mounting Storage class with pv and pvc using NFS.
Unfortunately, Amazon Elastic Block Store (EBS) volumes do not currently support the ReadWriteMany access mode in Kubernetes. EBS volumes are designed for ReadWriteOnce access, meaning they can only be attached to a single pod at a time. If you require shared read and write access to a volume from multiple pods, you may want to consider using a different storage solution that supports the ReadWriteMany access mode, such as a network file system (NFS) or a distributed storage system like GlusterFS or Ceph. Let me know if you have any further questions!
Thanks for the suggestion! I'll definitely create a video covering Networking and Certificate usage in Kubernetes. Stay tuned for the upcoming tutorial! If you have any more topics in mind, feel free to share. Your input is valuable!
In future, if I increase the storage from pvc 1gi to 12gi. Is that going to create new ebs or it will just increase the existing volume storage to 12gi. And if it creates new ebs then what will happen with those data inside the previously created ebs.?
Great question! In Kubernetes, there are several storage types, including local storage, network-attached storage (NAS), and block storage like EBS. Each serves different use cases. I've covered EBS Volume Provisioning in this video. Stay tuned for more in-depth explanations on various storage types!
The secret that was created is not mounted anywhere, will kubernetes directly read the secret to connect to AWS, or it needs to mounted on an object like storage class.
@@DevOpsPro k get events --watch 0s Normal ExternalProvisioning persistentvolumeclaim/ebs-claim Waiting for a volume to be created either by the external provisioner 'ebs.csi.aws.com' or manually by the system administrator. If volume creation is delayed, please verify that the provisioner is running and correctly registered. 0s Warning ProvisioningFailed persistentvolumeclaim/ebs-claim failed to provision volume with StorageClass "ebs-sc": rpc error: code = DeadlineExceeded desc = context deadline exceeded 0s Normal Provisioning persistentvolumeclaim/ebs-claim External provisioner is provisioning volume for claim "default/ebs-claim" 0s Warning ProvisioningFailed persistentvolumeclaim/ebs-claim failed to provision volume with StorageClass "ebs-sc": rpc error: code = DeadlineExceeded desc = context deadline exceeded 0s Normal Provisioning persistentvolumeclaim/ebs-claim External provisioner is provisioning volume for claim "default/ebs-claim" k logs ebs-csi-controller-54d6fc8879-4p8l8 --follow b2-7649cdd7cedc\": could not create volume in EC2: operation error EC2: CreateVolume, request canceled, context deadline exceeded" E0517 16:15:33.431541 1 driver.go:107] "GRPC error" err="rpc error: code = Internal desc = Could not create volume \"pvc-a5aab4c0-6dff-4d18-aeb2-7649cdd7cedc\": could not create volume in EC2: operation error EC2: CreateVolume, request canceled, context canceled" E0517 16:16:49.432798 1 driver.go:107] "GRPC error" err="rpc error: code = Internal desc = Could not create volume \"pvc-a5aab4c0-6dff-4d18-aeb2-7649cdd7cedc\": could not create volume in EC2: operation error EC2: CreateVolume, request canceled, context canceled"
i am getting this error "Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 31m default-scheduler Successfully assigned default/app to minikube Normal SuccessfulAttachVolume 31m attachdetach-controller AttachVolume.Attach succeeded for volume "pvc-7cfd1c5b-59ba-4bb0-a262-5a341615ea00" Warning FailedMount 20m (x2 over 22m) kubelet Unable to attach or mount volumes: unmounted volumes=[persistent-storage], unattached volumes=[kube-api-access-smb4g persistent-storage]: timed out waiting for the condition Warning FailedMount 8m49s (x8 over 29m) kubelet Unable to attach or mount volumes: unmounted volumes=[persistent-storage], unattached volumes=[persistent-storage kube-api-access-smb4g]: timed out waiting for the condition Warning FailedMount 24s (x23 over 31m) kubelet MountVolume.MountDevice failed for volume "pvc-7cfd1c5b-59ba-4bb0-a262-5a341615ea00" : rpc error: code = Internal desc = Failed to find device path /dev/xvdaa. no device path for device "/dev/xvdaa" volume "vol-06b4c44765da5b59d" found" while describing in pod "app" although i followed all the steps which you asked to. kindly provide the solution.
