Closed krisdock closed 5 years ago
Considering all the steps beyond the initial setup that you did, I think this is beyond the scope of the quickstart itself. If you have a working cluster but then after kubeadm reset
-> upgrade -> kubeadm init/join
you are having problems, you should raise a ticket with kubeadm
itself.
Going to close this ticket for now but if you think something is wrong with the original cluster that the quickstart gives you, please elaborate on the problems that exist prior to the additional steps.
What steps did you take and what happened: I brought up a Quick Start cluster, did a kubeadm reset, reset all iptables rules, upgraded kube* to 1.13.3, and reinitialized a cluster. Once up and Ready, I created a StorageClass and PVC. When I attempt to start a Pod referencing the PVC, it gets stuck in Pending with the following entry in the 'describe' output:
What did you expect to happen: For the Pod to start and the PVC to be mounted correctly.
Anything else you would like to add: I keep finding other "similar" issues references tags on the instances, but haven't found anything that fixes this.
Environment:
kubectl version
):/etc/os-release
):