Difference between revisions of "Aws-ebs-csi-driver"
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
[[helm repo update]] | [[helm repo update]] | ||
helm upgrade --install aws-ebs-csi-driver --namespace [[kube-system]] aws-ebs-csi-driver/aws-ebs-csi-driver | helm upgrade --install aws-ebs-csi-driver --namespace [[kube-system]] aws-ebs-csi-driver/aws-ebs-csi-driver | ||
| + | Release "aws-ebs-csi-driver" does not exist. Installing it now. | ||
| + | NAME: aws-ebs-csi-driver | ||
| + | LAST DEPLOYED: Mon Sep 26 08:02:42 2022 | ||
| + | NAMESPACE: [[kube-system]] | ||
| + | STATUS: deployed | ||
| + | REVISION: 1 | ||
| + | TEST SUITE: None | ||
| + | NOTES: | ||
| + | To verify that aws-ebs-csi-driver has started, run: | ||
| + | |||
| + | [[kubectl get pod -n kube-system]] -l "app.kubernetes.io/name=aws-ebs-csi-driver,app.kubernetes.io/instance=aws-ebs-csi-driver" | ||
| + | |||
| + | NOTE: The [CSI Snapshotter](https://github.com/kubernetes-csi/external-snapshotter) controller and CRDs will no longer be installed as part of this chart and moving forward will be a prerequisite of using the snap shotting functionality. | ||
Revision as of 06:03, 26 September 2022
default 8m51s Warning FailedScheduling pod/myprometheus-alertmanager-5967d4ff85-5glkh running PreBind plugin "VolumeBinding": binding volumes: timed out waiting for the condition default 4m58s Normal ExternalProvisioning persistentvolumeclaim/myprometheus-alertmanager waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator
helm repo add aws-ebs-csi-driver https://kubernetes-sigs.github.io/aws-ebs-csi-driver helm repo update helm upgrade --install aws-ebs-csi-driver --namespace kube-system aws-ebs-csi-driver/aws-ebs-csi-driver Release "aws-ebs-csi-driver" does not exist. Installing it now. NAME: aws-ebs-csi-driver LAST DEPLOYED: Mon Sep 26 08:02:42 2022 NAMESPACE: kube-system STATUS: deployed REVISION: 1 TEST SUITE: None NOTES: To verify that aws-ebs-csi-driver has started, run: kubectl get pod -n kube-system -l "app.kubernetes.io/name=aws-ebs-csi-driver,app.kubernetes.io/instance=aws-ebs-csi-driver"
NOTE: The [CSI Snapshotter](https://github.com/kubernetes-csi/external-snapshotter) controller and CRDs will no longer be installed as part of this chart and moving forward will be a prerequisite of using the snap shotting functionality.
aws-efs-csi-driver aws eks create-addon
See also
- CSI, Amazon EBS CSI driver, Kubernetes Filestore CSI driver, GKE CSI Driver
pd.csi.storage.gke.io, CSI Migration,aws-efs-csi-driver, aws-ebs-csi-driver, gcp_filestore_csi_driver_config,GcePersistentDiskCsiDriver, kind: CSINode, csi-hostpath-driver, Kubernetes snapshots - EKS,
eksctl, EKS add-ons, Amazon EKS cluster role, Terraform EKS, Kubernetes Autoscaler, Karpenter, Terraform module: EKS, Terraform resource: aws eks node group, Terraform data source: aws_eks_cluster, AWS Controllers for Kubernetes, AWS Load Balancer Controller, Amazon EKS Anywhere, Kustomize,aws-iam-authenticator, ACK, tEKS, Amazon EKS authorization, Amazon EKS authentication, Nodegroup, EKS storage,aws-ebs-csi-driver, aws-efs-csi-driver, aws-load-balancer-controller, amazon-vpc-cni-k8s, EKS security, EKS Best Practices Guides,hardeneks, EKS versions,fargate-scheduler,eks-connector, Resilience in Amazon EKS, EKS control plane logging, Security groups for Pods in EKS
Advertising:
