使用Helm 安装MySQL,缺省方式下发现pod一直处于pending状态,确认之后发现未创建足够PV所导致的问题。
问题现象
master $ kubectl get pods
NAME READY STATUS RESTARTS AGE
amber-ibex-mysql-5cd6bd76bb-hz8mh 0/1 Pending 0 74s
master $
环境说明
master $ kubectl version
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"clean", BuildDate:"2019-03-25T15:53:57Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"clean", BuildDate:"2019-03-25T15:45:25Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}
master $
master $ helm version
Client: &version.Version{SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"}
master $
步骤1: 安装mysql
master $ kubectl get pv
No resources found.
master $ kubectl get pvc
No resources found.
master $ helm install stable/mysql
NAME: amber-ibex
LAST DEPLOYED: Wed Dec 4 08:07:55 2019
NAMESPACE: default
STATUS: DEPLOYED
RESOURCES:
==> v1/Secret
NAME TYPE DATA AGE
amber-ibex-mysql Opaque 2 0s
==> v1/ConfigMap
NAME DATA AGE
amber-ibex-mysql-test 1 0s
==> v1/PersistentVolumeClaim
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
amber-ibex-mysql Pending 0s
==> v1/Service
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
amber-ibex-mysql ClusterIP 10.109.73.123 <none&