EKS AMI 1.20 - failed to create pod sandbox
Bug #1932116 reported by
Maurizio Valenzisi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Fix Released
|
High
|
Thomas Bechtold |
Bug Description
With the newest AMI for EKS with K8s 1.20.4,
some pods fail to start with the error:
Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "32f94d8f159e34
Cloud: AWS
AMI ID: ami-0e7501dc4c2
EKS K8s version: 1.20
Platform version: eks.1
Related branches
~toabctl/cloud-images/+git/aws-eks-website:1.20-update
Merged
into
~cloud-images-release-managers/cloud-images/+git/aws-eks-website:master
at
revision e43114838aeec3a8ac1e0d98d95117f898b45bca
- Gauthier Jolly: Approve
- Joshua Powers (community): Approve
-
Diff: 4513 lines (+2230/-2221)1 file modifiedindex.html (+2230/-2221)
Changed in cloud-images: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
boostrap.sh:
MIME-Version: 1.0 "==BOUNDARY= ="
Content-Type: multipart/mixed; boundary=
--==BOUNDARY== NAME=devops- ops-k8s- cluster --node- labels= node-selector- key=non- production, eks.amazonaws. com/nodegroup- image=ami- 0e7501dc4c24cda 7c,cluster= devops- ops-k8s- ekscluster- id,eks. amazonaws. com/capacityTyp e=ON_DEMAND, eks.amazonaws. com/nodegroup= jenkins- 20210614, environment- type=non- production bootstrap. sh $CLUSTER_NAME --kubelet- extra-args "$NODE_LABELS $NODE_TAINTS"
Content-Type: text/x-shellscript; charset="us-ascii"
#!/bin/bash
set -x
CLUSTER_
NODE_LABELS=
NODE_TAINTS=
/etc/eks/
--==BOUNDARY==--