Etcd fails Clair scan for high risk vulnerabilities

[eak13]

Describe the bug
Clair scans have identified several high risk vulnerabilities in Etcd. See attached for details.
This is a tracking issue to ensure that the images used by Airshipctl are updated once the vulnerabilities have been resolved.

Version of etcd which was evaluated is v3.4.3 for etcd. Etcd versions is determined based on Kubernetes/kubeadm versions.

Steps To Reproduce
Run Clair scan against the images.

Expected behavior
No high risk security vulnerabilities are found.
etcd-4198ba6-2021-05-31_15-52-04.txt

[sshiba]

Hi Andrew, can you assign this issue to me? Thanks

[sshiba]

Here is what I found for kubernetes v1.20 for etcd:

COMPONENT                 CURRENT    AVAILABLE
kube-apiserver            v1.19.6    v1.20.1
kube-controller-manager   v1.19.6    v1.20.1
kube-scheduler            v1.19.6    v1.20.1
kube-proxy                v1.19.6    v1.20.1
CoreDNS                   1.7.0      1.7.0
etcd                      3.4.13-0   3.4.13-0

Run Clair in jenkins job (etcd:3.4.13-0) and it passed (https://jenkins-nc.wnv2b.cci.att.com/job/images/job/open-images/1401/console).

What should be the next step? Provide recommendations for kubernetes v1.20.x?

[eak13]

We are upgrade K8s, so accepting this