Addon headlamp: Update headlamp-k8s/headlamp image from v0.24.1 to v0.25.0

[joaquimrocha]

Upgrade Headlamp version to 0.25.0
cc: @joaquimrocha

[k8s-ci-robot]

Hi @joaquimrocha. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[minikube-bot]

Can one of the admins verify this patch?

[medyagh]

@joaquimrocha please consider making this an automation job in github action
here is a simmilar job for kong addon.

https://github.com/kubernetes/minikube/blob/master/.github/workflows/update-kong-version.yml

you would need to make a new make target "make update-headlamp", let me know if you have any questions on it

[joaquimrocha]

Hey @medyagh . Thanks, that sounds very cool. Our PRs are automated anyway, but I like the idea of having the action in the minikube repo instead.
If you agree, we could merge this PR so the addon is not delayed and we'll submit the new action before our next release. WDYT?

[medyagh]

sounds good ! btw I am curious thats good where do you run the automation ? look forward to see more contributions for you :)

[medyagh]

/ok-to-test

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: joaquimrocha, medyagh

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 [medyagh]

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

[minikube-pr-bot]

kvm2 driver with docker runtime

+-------------------+----------+---------------------+
|      COMMAND      | MINIKUBE | MINIKUBE (PR 19349) |
+-------------------+----------+---------------------+
| ⚠️  minikube start | 48.3s    | 71.6s ⚠️             |
| enable ingress    | 24.9s    | 25.8s               |
+-------------------+----------+---------------------+

Times for minikube start: 50.1s 46.7s 47.9s 49.3s 47.4s
Times for minikube (PR 19349) start: 52.0s 48.2s 46.8s 51.4s 159.8s

Times for minikube ingress: 27.5s 23.4s 25.4s 24.0s 24.0s
Times for minikube (PR 19349) ingress: 25.0s 24.0s 27.9s 28.0s 24.0s

docker driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 19349) |
+----------------+----------+---------------------+
| minikube start | 21.8s    | 22.8s               |
| enable ingress | 21.8s    | 21.9s               |
+----------------+----------+---------------------+

Times for minikube start: 24.2s 20.4s 21.2s 22.2s 21.0s
Times for minikube (PR 19349) start: 24.7s 24.7s 21.4s 21.3s 22.1s

Times for minikube ingress: 21.3s 21.8s 21.8s 22.8s 21.3s
Times for minikube (PR 19349) ingress: 21.3s 23.3s 21.3s 21.8s 21.8s

docker driver with containerd runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 19349) |
+----------------+----------+---------------------+
| minikube start | 22.4s    | 22.3s               |
| enable ingress | 45.0s    | 48.4s               |
+----------------+----------+---------------------+

Times for minikube start: 22.7s 20.7s 23.3s 21.1s 24.1s
Times for minikube (PR 19349) start: 19.7s 22.8s 22.9s 22.6s 23.4s

Times for minikube ingress: 48.3s 48.3s 47.2s 49.3s 31.8s
Times for minikube (PR 19349) ingress: 47.8s 48.3s 48.3s 48.3s 49.3s

[minikube-pr-bot]

Here are the number of top 10 failed tests in each environments with lowest flake rate.

Environment	Test Name	Flake Rate
Docker_Linux_containerd_arm64 (2 failed)	TestStartStop/group/old-k8s-version/serial/SecondStart(gopogh)	46.95% (chart)

Besides the following environments also have failed tests:

• QEMU_macOS: 97 failed (gopogh)

• Docker_Linux_crio_arm64: 2 failed (gopogh)

• Docker_Linux_crio: 2 failed (gopogh)

• KVM_Linux_crio: 30 failed (gopogh)

• Hyperkit_macOS: 24 failed (gopogh)

• Docker_Cloud_Shell: 5 failed (gopogh)

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