Kubernetes 上的 MySQL - pod 具有未绑定的 immeidate persistentVolumeClaim
[英]MySQL on Kubernetes - pod has unbound immeidate persistentVolumeClaim
问题描述
I tried deploying MySQL on Kubernetes as mentioned in https://kubernetes.io/docs/tasks/run-application/run-replicated-stateful-application/ .
我尝试在 Kubernetes 上部署 MySQL，如https://kubernetes.io/docs/tasks/run-application/run-replicated-stateful-application/ 中所述。 But, running into the below error.但是，遇到以下错误。
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling 27s (x6 over 72s) default-scheduler pod has unbound immediate PersistentVolumeClaims (repeated 99 times)
Warning FailedScheduling 0s (x14 over 94s) default-scheduler pod has unbound immediate PersistentVolumeClaims (repeated 100 times)
Not sure what is wrong with this?不知道这有什么问题？ Can i remove volumeClaimTemplates and create a separate persistentVolumeClaim?我可以删除volumeClaimTemplates 并创建一个单独的persistentVolumeClaim 吗？
1 个解决方案
解决方案1
1 2020-03-06 05:20:24
In the doc its mentioned在文档中提到
You need to either have a dynamic PersistentVolume provisioner with a default StorageClass , or statically provision PersistentVolumes yourself to satisfy the PersistentVolumeClaims used here
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.