Please include the following as well: k8s.gcr.io/etcd:3.4.3-0 The full list is: k8s.gcr.io/kube-apiserver:v1.18.1 k8s.gcr.io/kube-controller-manager:v1.18.1 k8s.gcr.io/kube-scheduler:v1.18.1 k8s.gcr.io/kube-proxy:v1.18.1 k8s.gcr.io/pause:3.2 k8s.gcr.io/etcd:3.4.3-0 k8s.gcr.io/coredns:1.6.7 Previously, I only checked the list of deployed images in the cluster. Since we run etcd natively this is not deployed in the cluster, but is still required to be pulled as part of bringing up Kubernetes. Bob From: "Jascanu, Nicolae" <nicolae.jascanu@intel.com> Date: Wednesday, April 15, 2020 at 12:52 PM To: Robert Church <Robert.Church@windriver.com>, "'starlingx-discuss@lists.starlingx.io'" <starlingx-discuss@lists.starlingx.io> Subject: RE: Kubernetes upgrade to v1.18.1 Hi Robert, Thank you for the announcement. We’ve pushed the images on the local repository. Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania From: Church, Robert <Robert.Church@windriver.com> Sent: Wednesday, April 15, 2020 00:22 To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Kubernetes upgrade to v1.18.1 As part of updating the container components for STX 4.0, changes have been merged to enable the latest release of Kubernetes: https://review.opendev.org/#/q/topic:k8s_upversion+(status:open+OR+status:me...) Anyone behind a firewall who pulls docker images into a local repository will need to grab some updated images: k8s.gcr.io/coredns:1.6.7 k8s.gcr.io/kube-apiserver:v1.18.1 k8s.gcr.io/kube-controller-manager:v1.18.1 k8s.gcr.io/kube-proxy:v1.18.1 k8s.gcr.io/kube-scheduler:v1.18.1 k8s.gcr.io/pause:3.2 Bob