Build(deps): Bump github.com/docker/cli from 27.1.0+incompatible to 27.1.1+incompatible

[dependabot[bot]]

Bumps github.com/docker/cli from 27.1.0+incompatible to 27.1.1+incompatible.

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[minikube-bot]

Can one of the admins verify this patch?

[k8s-ci-robot]

Hi @dependabot[bot]. 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](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot] Once this PR has been reviewed and has the lgtm label, please assign medyagh for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files: - **[OWNERS](https://github.com/kubernetes/minikube/blob/master/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[medyagh]

/ok-to-test

[minikube-pr-bot]

kvm2 driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 19347) |
+----------------+----------+---------------------+
| minikube start | 50.8s    | 52.0s               |
| enable ingress | 25.8s    | 27.0s               |
+----------------+----------+---------------------+

Times for minikube start: 50.6s 50.6s 52.1s 48.6s 52.0s Times for minikube (PR 19347) start: 51.0s 52.2s 51.6s 51.4s 53.7s Times for minikube ingress: 28.0s 24.5s 25.0s 24.1s 27.5s Times for minikube (PR 19347) ingress: 24.0s 27.6s 27.6s 28.0s 28.0s

docker driver with docker runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 19347) |
+----------------+----------+---------------------+
| minikube start | 23.6s    | 24.1s               |
| enable ingress | 21.9s    | 21.7s               |
+----------------+----------+---------------------+

Times for minikube ingress: 23.8s 21.3s 21.8s 21.3s 21.3s Times for minikube (PR 19347) ingress: 21.3s 21.8s 22.3s 21.8s 21.3s Times for minikube start: 24.6s 22.1s 22.1s 24.0s 25.2s Times for minikube (PR 19347) start: 24.4s 24.7s 24.9s 24.4s 22.3s

docker driver with containerd runtime

+----------------+----------+---------------------+
|    COMMAND     | MINIKUBE | MINIKUBE (PR 19347) |
+----------------+----------+---------------------+
| minikube start | 22.2s    | 21.9s               |
| enable ingress | 46.5s    | 47.7s               |
+----------------+----------+---------------------+

Times for minikube start: 23.1s 20.7s 24.0s 23.2s 20.2s Times for minikube (PR 19347) start: 20.5s 24.1s 23.7s 20.3s 20.8s Times for minikube ingress: 48.8s 47.8s 48.3s 47.8s 39.8s Times for minikube (PR 19347) ingress: 48.3s 46.8s 47.8s 47.8s 47.8s

[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_crio_arm64 (3 failed)	TestFunctional/parallel/PersistentVolumeClaim(gopogh)	2.56% (chart)
Docker_Linux_docker_arm64 (1 failed)	TestStartStop/group/old-k8s-version/serial/SecondStart(gopogh)	6.45% (chart)
KVM_Linux (1 failed)	TestMultiControlPlane/serial/DeployApp(gopogh)	0.65% (chart)
Docker_Linux_containerd_arm64 (2 failed)	TestStartStop/group/old-k8s-version/serial/SecondStart(gopogh)	45.86% (chart)

Besides the following environments also have failed tests:

• KVM_Linux_crio: 29 failed (gopogh)

• Docker_Linux_crio: 2 failed (gopogh)

• QEMU_macOS: 97 failed (gopogh)

• Docker_Cloud_Shell: 5 failed (gopogh)

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