Helm:问题对应:缺少PV或者PV不足导致pod一直pending的对应方法

使用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&
  • 3
    点赞
  • 9
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值