search

heptio / aws-quickstart

AWS Kubernetes cluster via CloudFormation and kubeadm
Apache License 2.0
223 stars 134 forks source link

PV/PVC issue when I update to 1.13.3 #247

Closed krisdock closed 5 years ago

krisdock commented 5 years ago

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:

Warning  FailedScheduling  0s (x3 over 0s)    default-scheduler  0/2 nodes are available: 1 node(s) had taints that the pod didn't tolerate, 1 node(s) had volume node affinity conflict.

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:

Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.3", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"clean", BuildDate:"2019-02-01T20:08:12Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.3", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"clean", BuildDate:"2019-02-01T20:00:57Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
NAME="Ubuntu"
VERSION="16.04.5 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.5 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
johnSchnake commented 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.