Kubernetes无法在AWS-EBS上创建PersistentVolumeClaim [英] Kubernetes Failed to Create PersistentVolumeClaim on AWS-EBS
问题描述
我使用kubeadm
设置了具有四个EC2实例的Kubernetes集群. Kubernetes集群工作正常,但在尝试创建PersistentVolumeClaim
时失败.
I setup a Kubernetes cluster with four EC2 instances using kubeadm
. The Kubernetes cluster works fine, but failed when I try to create a PersistentVolumeClaim
.
首先,我用下面的YAML创建了StorageClass
,效果很好.
First I created a StorageClass
with following YAML which works fine.
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: generic
annotations:
storageclass.kubernetes.io/is-default-class: "true"
provisioner: kubernetes.io/aws-ebs
parameters:
type: gp2
encrypted: "false"
然后,我尝试使用以下YAML创建PersistentVolumeClaim
:
Then I try to create a PersistentVolumeClaim
with the following YAML:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: slow
labels:
app: nginx
spec:
storageClassName: generic
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 3Gi
哪个出现以下错误消息:
Which got an error message of:
无法使用StorageClass"Generic"配置卷:无法获取AWS Cloud Provider. GetCloudProvider返回了< nil>代替
Failed to provision volume with StorageClass "generic": Failed to get AWS Cloud Provider. GetCloudProvider returned <nil> instead
顺便说一句,似乎从未创建过PersistentVolume
.
By the way, it seems no PersistentVolume
was ever created.
kubectl get pv
No resources found.
有什么办法解决这个问题吗?
Any ideas how to solve this?
谢谢.
推荐答案
这是因为在运行kubeadm init时没有使用选项--cloud-provider=aws
.
This is because you didn't use the option --cloud-provider=aws
while running kubeadm init
kubeadm --cloud-provider=aws init ...
或者,您应该将云提供程序信息(cloudProvider)放入配置文件中,它将在初始化期间将云提供程序标志添加到api和控制器管理器中:
Alternatively, you should put the cloud provider info ( cloudProvider ) into your config file and it will add the cloud provider flag to api and controller manager during initialization :
apiVersion: kubeadm.k8s.io/v1alpha1
kind: MasterConfiguration
etcd:
endpoints:
- "http://my-etcd1"
- "http://my-etcd2"
- "http://my-etcd3"
cloudProvider: aws
apiServerExtraArgs:
apiserver-count: 3
apiServerCertSANs:
- "my-master-hostname1"
- "my-master-hostname2"
- "my-master-hostname3"
- "10.10.0.50"
- "10.10.0.51"
- "10.10.0.52"
- "127.0.0.1"
token: "my-kube-token"
tokenTTL: "0"
更多信息: https://medium.com/jane-ai-engineering-blog/kubernetes-on-aws-6281e3a830fe
这篇关于Kubernetes无法在AWS-EBS上创建PersistentVolumeClaim的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!