WIP: efk addon: Update images

[spowelljr]

Closes #15280

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: spowelljr

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [spowelljr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[spowelljr]

/ok-to-test

[minikube-pr-bot]

kvm2 driver with docker runtime

+-------------------+----------+---------------------+
|      COMMAND      | MINIKUBE | MINIKUBE (PR 16343) |
+-------------------+----------+---------------------+
| minikube start    | 52.0s    | 52.8s               |
| ⚠️  enable ingress | 25.9s    | 38.1s ⚠️             |
+-------------------+----------+---------------------+

Times for minikube start: 51.6s 51.0s 54.0s 51.8s 51.7s
Times for minikube (PR 16343) start: 56.3s 52.6s 51.0s 50.9s 53.0s

Times for minikube ingress: 25.2s 25.2s 26.2s 28.1s 24.7s
Times for minikube (PR 16343) ingress: 25.2s 25.8s 26.7s 28.2s 84.7s

docker driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 16343) |
+----------------+----------+---------------------+
| minikube start | 22.9s    | 22.5s               |
| enable ingress | 39.5s    | 32.9s               |
+----------------+----------+---------------------+

Times for minikube (PR 16343) ingress: 21.0s 21.5s 50.5s 22.0s 49.5s
Times for minikube ingress: 50.9s 82.0s 21.5s 22.0s 21.0s

Times for minikube start: 24.7s 24.5s 22.0s 21.5s 21.9s
Times for minikube (PR 16343) start: 21.5s 22.2s 24.8s 21.8s 22.2s

docker driver with containerd runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 16343) |
+----------------+----------+---------------------+
| minikube start | 21.7s    | 20.9s               |
| enable ingress | 38.0s    | 35.5s               |
+----------------+----------+---------------------+

Times for minikube start: 24.5s 20.8s 23.2s 20.3s 19.9s
Times for minikube (PR 16343) start: 20.6s 20.3s 22.7s 20.5s 20.3s

Times for minikube ingress: 47.5s 32.0s 31.0s 47.5s 32.0s
Times for minikube (PR 16343) ingress: 49.0s 32.0s 33.0s 31.5s 32.0s

[minikube-pr-bot]

These are the flake rates of all failed tests.

Environment	Failed Tests	Flake Rate (%)
Docker_Linux	TestStartStop/group/default-k8s-diff-port/serial/AddonExistsAfterStop (gopogh)	0.00 (chart)
Docker_Linux	TestStartStop/group/default-k8s-diff-port/serial/Pause (gopogh)	0.00 (chart)
Docker_Linux	TestStartStop/group/default-k8s-diff-port/serial/SecondStart (gopogh)	0.00 (chart)
Docker_Linux	TestStartStop/group/default-k8s-diff-port/serial/UserAppExistsAfterStop (gopogh)	0.00 (chart)
Docker_Linux	TestStartStop/group/default-k8s-diff-port/serial/VerifyKubernetesImages (gopogh)	0.00 (chart)
Docker_macOS	TestSkaffold (gopogh)	22.22 (chart)
Docker_Windows	TestPause/serial/SecondStartNoReconfiguration (gopogh)	22.34 (chart)
Hyper-V_Windows	TestNoKubernetes/serial/StartWithK8s (gopogh)	33.94 (chart)

To see the flake rates of all tests by environment, click here.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle rotten
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten