Enable the ingress controller

[chuttmateo]

Los comandos necesarios para reproducir la incidencia:
-minikube start
-minikube addons enable ingress
El resultado completo del comando que ha fallado:
minikube start
😄 minikube v1.31.2 en Ubuntu 22.04
✨ Controlador docker seleccionado automáticamente. Otras opciones: none, ssh
📌 Using Docker driver with root privileges
👍 Starting control plane node minikube in cluster minikube
🚜 Pulling base image ...
🔥 Creando docker container (CPUs=2, Memory=2200MB) ...
🐳 Preparando Kubernetes v1.27.4 en Docker 24.0.4...
▪ Generando certificados y llaves
▪ Iniciando plano de control
▪ Configurando reglas RBAC...
🔗 Configurando CNI bridge CNI ...
🔎 Verifying Kubernetes components...
▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
🌟 Complementos habilitados: storage-provisioner, default-storageclass
🏄 Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default

mateo@mateo-MS-7641:~/proyectos/personales/ejercicios-kubernetes/curso/ingress$ minikube addons enable ingress
💡 ingress is an addon maintained by Kubernetes. For any concerns contact minikube on GitHub.
You can view the list of minikube maintainers at: https://github.com/kubernetes/minikube/blob/master/OWNERS
▪ Using image registry.k8s.io/ingress-nginx/controller:v1.8.1
▪ Using image registry.k8s.io/ingress-nginx/kube-webhook-certgen:v20230407
▪ Using image registry.k8s.io/ingress-nginx/kube-webhook-certgen:v20230407
🔎 Verifying ingress addon...

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

╭───────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ 😿 If the above advice does not help, please let us know: │
│ 👉 https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ Please run minikube logs --file=logs.txt and attach logs.txt to the GitHub issue. │
│ Please also attach the following file to the GitHub issue: │
│ - /tmp/minikube_addons_cc77b0effb423880e70838ec98a13c8912e1d135_0.log │
│ │
╰───────────────────────────────────────────────────────────────────────────────────────────╯

El resultado del comando minikube logs:
logs.txt

La versión del sistema operativo que utilizaste:
Ubuntu 22.04

[lanlangdeai]

I have the same problem. Have you solved it?

[spowelljr]

Hi @chuttmateo, could you run kubectl get pods -n ingress-nginx to get the name of the pod that's failing. And then run the following and post them here:

kubectl describe pods <pod_name> -n ingress-nginx
kubectl logs <pod_name> -n ingress-nginx

---

Hola @chuttmateo, ¿podrías ejecutar kubectl get pods -n ingress-nginx para obtener el nombre del pod que está fallando? Y luego ejecute lo siguiente y publíquelos aquí:

kubectl describe pods <pod_name> -n ingress-nginx
kubectl logs <pod_name> -n ingress-nginx

[chuttmateo]

hi @lanlangdeai no yet.

[chuttmateo]

Sure, @spowelljr . Here, there is a history of commands, an edited file 'console-logs,' as well as another non-edited file 'logs'.

1994 minikube start
1995 minikube addons enable ingress
1996 kubectl get pods -n ingress-nginx
1997 kubectl describe pods ingress-nginx-admission-create-fcmz2 -n ingress-nginx
1998 kubectl logs ingress-nginx-admission-create-fcmz2 -n ingress-nginx
1999 kubectl describe pods ingress-nginx-admission-patch-46lsb -n ingress-nginx
2000 kubectl logs ingress-nginx-admission-patch-46lsb -n ingress-nginx
2001 kubectl describe pods ingress-nginx-controller-7799c6795f-cbqbn -n ingress-nginx
2002 kubectl logs ingress-nginx-controller-7799c6795f-cbqbn -n ingress-nginx

console-logs.txt

logs.txt

[spowelljr]

Thanks for the logs @chuttmateo, you seem to be experiencing this issue here

kubernetes/ingress-nginx#5932

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten