Cannot start ingress addon: waiting for pod #10544
Comments
|
I checked the logs and see this I've also set NO_PROXY |
ilya-zuyev
added
kind/support
|
Hey @newtoniumx3 thanks for opening this issue. Could you provide more details around the pods so we can figure out why the image isn't being pulled? If you have docker running, I'm also curious if this happens with the docker driver as well? If you could try: that should let us know if it works with ingress. |
priyawadhwa
added
the
triage/needs-information
Hey I’m currently afraid to touch it as I finally got everything working using Kubernetes that ships with docker desktop. I will attempt on different machine to see if I can reproduce it. |
priyawadhwa
removed
the
triage/needs-information
|
@newtoniumx3 thanks, no worries if it's too difficult to try to reproduce! |
|
@newtoniumx3 I'm going to close this issue, but if you end up being able to reproduce the issue feel free to reopen. |
|
I'm seeing this same issue when enabling the ingress addon. Let me know what other information would be helpful here. |
|
@newtoniumx3 do u mind trying with latest version of minikube again, we fixed an inagress bug in v1.20.0 that could help with this ? |
|
@medyagh I gave v1.20.0 a try, but unfortunately, the error still occurs for me. |
|
Same issue happened for me , any suggestion to fix it ? |
|
In my case, apache o ubunto was using port 80 |
spowelljr
changed the title
spowelljr
added
addon/ingress
area/addons
and removed
co/hyperv
|
+1, i'm also seeing this issue. Will do more debugging. |
|
Output of |
|
@adamf Can you do a fresh setup and send the logs? I'm having trouble recreating the issue. Also add any driver settings and make sure to paste them here. |
you can pull image from dockerhub docker pull pollyduan/ingress-nginx-controller:v0.44.0 docker tag pollyduan/ingress-nginx-controller:v0.44.0 k8s.gcr.io/ingress-nginx/controller:v0.44.0 |
kubectl edit pods ingress-nginx-controller-7b8cbd57c9-jnzmd -n ingress-nginx and change to 'image: k8s.gcr.io/ingress-nginx/controller:v0.44.0'， I hope these can help |
I had tried like this before I pasted here, it's still something wrong with it |
It's like image not pulled , but the log below looks like pulled success. kube connect this |
|
I think I know why, it because the China's great GFW build by you know who. In the minikube , here is a But in some reason, it not available. so I get that error. If other dude in China, not use solutionIn
The second is a personal image just mirror And then rename tag to what you need, and then I think the registry of |
|
I had the same issue with 'minikube addons enable ingress' command. I faced this image downloading issue during other scenarios also and had to use the same - switch ISP solution.
|
@yangyaofei do you think this PR helps ? |
Hi @medyagh thank you to let me know this. Actually, I'm a starter with this. so I don't know it will help or not . But I saw #11785 , I think this will be helped. And I have a suggest that is add more error message when cannot pull the image, and add little more document about it and a general solution for this. There are two types dev in china, one is read official doc and use google, another is read chinese blog and use baidu . The devs only use baidu will follow the chinese blog and probably use the version build by alibaba( aliyun ), The devs can use google, only thing they need is to know why this error occur, and then they can solve it by this own or with a simple guide with few sentences. And for #11785 , it's good. I'm not sure that For the record, same block for the ghcr and other repo, so technically is not the problem of minikube or gcr 😂😂😂 |
spowelljr
added
priority/important-longterm
|
I had same problem. There is how I solved it: An error: The solution:
Note: Value of |
|
I'm in china and here is my way to solve this problem: I found no matter how I specify the "ingress": NewAddon([]*BinAsset{
MustBinAsset(addons.IngressAssets,
"ingress/ingress-deploy.yaml.tmpl",
vmpath.GuestAddonsDir,
"ingress-deploy.yaml",
"0640"),
}, false, "ingress", "", map[string]string{
// https://github.com/kubernetes/ingress-nginx/blob/557604f4ef526f7755d36089b617bc7686c389f9/deploy/static/provider/kind/deploy.yaml#L323
"IngressController": "ingress-nginx/controller:v1.0.0-beta.3@sha256:44a7a06b71187a4529b0a9edee5cc22bdf71b414470eff696c3869ea8d90a695",
// https://github.com/kubernetes/ingress-nginx/blob/557604f4ef526f7755d36089b617bc7686c389f9/deploy/static/provider/kind/deploy.yaml#L612
"KubeWebhookCertgenCreate": "k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.0@sha256:f3b6b39a6062328c095337b4cadcefd1612348fdd5190b1dcbcb9b9e90bd8068",
// https://github.com/kubernetes/ingress-nginx/blob/557604f4ef526f7755d36089b617bc7686c389f9/deploy/static/provider/kind/deploy.yaml#L660
"KubeWebhookCertgenPatch": "k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.0@sha256:f3b6b39a6062328c095337b4cadcefd1612348fdd5190b1dcbcb9b9e90bd8068",
}, map[string]string{
"IngressController": "k8s.gcr.io",
}),func NewAddon(assets []*BinAsset, enabled bool, addonName string, maintainer string, images map[string]string, registries map[string]string) *Addon {
a := &Addon{
Assets: assets,
enabled: enabled,
addonName: addonName,
Maintainer: maintainer,
Images: images,
Registries: registries,
}
return a
}So I use For others: Some suggestions: |
|
I got the same issue when running
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.3", GitCommit:"c92036820499fedefec0f847e2054d824aea6cd1", GitTreeState:"clean", BuildDate:"2021-10-27T18:41:28Z", GoVersion:"go1.16.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.3", GitCommit:"c92036820499fedefec0f847e2054d824aea6cd1", GitTreeState:"clean", BuildDate:"2021-10-27T18:35:25Z", GoVersion:"go1.16.9", Compiler:"gc", Platform:"linux/amd64"}
- Docker Version: It's been said in the detail mode .
Client: Docker Engine - Community
Version: 20.10.10
API version: 1.41
Go version: go1.16.9
Git commit: b485636
Built: Mon Oct 25 07:42:59 2021
OS/Arch: linux/amd64
Context: default
Experimental: true
Server: Docker Engine - Community I even tested out this approach:
Hint: I first enabled the ingress add-on and then went for the Mandatory ingress-nginx services. The result was confusing. It went all good for all of them with the exception of the last 2 items on the list.
What's wrong with them? |
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
k8s-ci-robot
added
the
lifecycle/stale
|
there seem to be potentially multiple different/similar problems reported and also several solutions/workarounds in this issue (specifically around firewalls) and we've implemented a number of improvements in the meantime (last being #13439 that's merger but not yet released), so I'll close this issue now and please open a new one if you still face issues with the ingress addon thank you /close |
|
I have tried all the suggestions in this thread but still having this issue? What is the final solution? |
|
|
Even if I managed to manually pull the 2 images related to enabling ingress, the |
I failed after using your method(network proxy were running on my local machine): |
|
In my situation, the main issue is that the images were not successfully pulled. I tried So I edited the pods and removed the kubectl -n ingress-nginx edit pod ingress-nginx-admission-create-xxxx
kubectl -n ingress-nginx edit pod ingress-nginx-admission-patch-xxxx
kubectl -n ingress-nginx edit pod ingress-nginx-controller-xxxxe.g.: After modification, there is no need to manually pull the images, the images will be pulled automatically. Finally, try minikube addons enable ingressAnd it works! If you are in China, try to add minikube start \
--image-mirror-country=cn \
--image-repository=registry.cn-hangzhou.aliyuncs.com/google_containers \
--force \
--addons ingressI hope these could help somebody! |
it works, very good
minikube_addons_1ba5e275a043117389ed64b6bf4c3b62e1556582_0.log |
Thank you so much! That's exactly the solution in my case! I am using Windows 11 and minikube in hyper-v driver! I was searching about the problem more than 1 day! |
非常棒，用这个方法解决了 |
and others
Steps to reproduce the issue:
minikube start --vm-driver hyperv --cpus 2 --memory=8192minikube addons enable ingress --alsologtostderrFull output of failed command:
Windows 10
Docker version 20.10.2, build 2291f61
minikube version: v1.17.1
commit: 043bdca
The text was updated successfully, but these errors were encountered: