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

Failed to pull image "quay.io/kubernetes-ingress-controller/nginx-ingress-controller:master": rpc error: code = Unknown desc = Error response from daemon: manifest for quay.io/kubernetes-ingress-controller/nginx-ingress-controller:master not found #4890

Closed
RomelBu opened this issue Jan 6, 2020 · 5 comments

Comments

@RomelBu
Copy link

RomelBu commented Jan 6, 2020

I had a stable nginx-ingress deployment automation that deploys on EKS, and uses Kustomize, which refers to the following resources:

- github.com/kubernetes/ingress-nginx/deploy/cluster-wide
- github.com/kubernetes/ingress-nginx/deploy/aws/l7

It was stable for about 8 months, then it started failing after January 1, 2020 with the error below:
Failed to pull image "quay.io/kubernetes-ingress-controller/nginx-ingress-controller:master": rpc error: code = Unknown desc = Error response from daemon: manifest for quay.io/kubernetes-ingress-controller/nginx-ingress-controller:master not found
Is this related to bcc7d98?

@aledbf
Copy link
Member

aledbf commented Jan 6, 2020

Is this related to bcc7d98?

Yes. Please check the docs https://kubernetes.github.io/ingress-nginx/deploy/#prerequisite-generic-deployment-command where you can see we point to a tag now.

@aledbf
Copy link
Member

aledbf commented Jan 6, 2020

Closing. Please check the docs and use a particular tag to install the ingress controller.

Using master will install the dev image.

@aledbf aledbf closed this as completed Jan 6, 2020
@RomelBu
Copy link
Author

RomelBu commented Jan 6, 2020

I'm not sure what went on, but my issue got resolved without code change on my end. It's as if the quay.io/kubernetes-ingress-controller/nginx-ingress-controller:master became available all of a sudden. Anyway, I'll try changing my code so it uses a tagged version.

Thanks!

@RomelBu
Copy link
Author

RomelBu commented Jan 6, 2020

The kustomization.yml that I have (used in my stable deployment) is pretty much the same as what was posted here #4156, by the OP of that old issue. My question now is, how to make it refer to the tagged artifacts? I'm looking for a way to make it work, so I tried github.com/kubernetes/ingress-nginx/tree/nginx-0.26.2/deploy/cluster-wide/, but it did not work -- I'm not that knowledgeable with github, so there's that, too.

kustomization.yml:

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: ingress-nginx
bases:
- github.com/kubernetes/ingress-nginx/deploy/cluster-wide
- github.com/kubernetes/ingress-nginx/deploy/aws/l7

@aledbf
Copy link
Member

aledbf commented Jan 6, 2020

@RomelBu please ask this question in the kustomize project

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants