Ingress Addon Fails to Enable Due to Context Deadline Exceeded Error

[kimutaieddy]

What Happened?

Issue Description
I'm experiencing an issue when trying to enable the Ingress addon in Minikube. The process fails with a context deadline exceeded error. Several Kubernetes components seem to fail during post-start hooks.

Encounter the error: MK_ADDON_ENABLE: enable failed: run callbacks: running callbacks: [waiting for app.kubernetes.io/name=ingress-nginx pods: context deadline exceeded].

Environment

• Minikube version: v1.33.1
• OS: Windows 11
• Docker version: 27.1.1
• Minikube driver: Docker

Attach the log file

logs.txt

Operating System

Windows

Driver

Docker

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 issue is closed

You can:

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

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

/lifecycle stale