Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

minikube (1.33.1) not able to pull images of nginx ingress #19405

Open
anishagoyal0504 opened this issue Aug 12, 2024 · 3 comments
Open

minikube (1.33.1) not able to pull images of nginx ingress #19405

anishagoyal0504 opened this issue Aug 12, 2024 · 3 comments
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@anishagoyal0504
Copy link

anishagoyal0504 commented Aug 12, 2024

What Happened?

I have minikube cluster and trying to enable nginx ingress using "minikube addons enable ingress" it is failing with timing out error

I am using minikube version 1.33.1

can someone guide me please

Attach the log file

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

Further looking at one of the pods logs:

Failed to pull image "registry.k8s.io/ingress-nginx/kube-webhook-certgen:v1.4.1@sha256:36d05b4077fg5453d13663702fa337f124675ba8667cbd949c03a8e8ea6fa4366": Error response from daemon: Get "https://registry.k8s.io/v2/": tls: failed to verify certificate: x509: certificate signed by unknown authority

Operating System

Redhat/Fedora

Driver

Docker

@kundan2707
Copy link
Contributor

/kind support

@k8s-ci-robot k8s-ci-robot added the kind/support Categorizes issue or PR as a support question. label Aug 12, 2024
@kundan2707
Copy link
Contributor

@anishagoyal0504 check your machine/VM for necessary PEM file to resolve certificate issue.

@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants