ingress-nginx: Error: INSTALLATION FAILED: failed pre-install: timed out waiting for the condition in k8s `1.24.1`

i’m trying to install ingress-nginx using helm on k8s cluster, but i receive below error Error: INSTALLATION FAILED: failed pre-install: timed out waiting for the condition

i use k8s version 1.24.1 (screenshot attached) image

i installed the k8s cluster using kubeadm The commands i used to install ingress-nginx using helm are present in the attached screenshot.

image

Please let me know how to fix this issue.

i didnot face this issue with k8s v1.22.9 image

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 40 (15 by maintainers)

Most upvoted comments

I reverted my cluster to k8s 1.22, as suggested by @Divine1 in the OP, but am getting the same issue:

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.11", GitCommit:"5824e3251d294d324320db85bf63a53eb0767af2", GitTreeState:"clean", BuildDate:"2022-06-16T05:39:23Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.11", GitCommit:"5824e3251d294d324320db85bf63a53eb0767af2", GitTreeState:"clean", BuildDate:"2022-06-16T05:33:55Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}

$ helm install --create-namespace --namespace ingress-nginx ingress-nginx ingress-nginx/ingress-nginx --debug
install.go:178: [debug] Original chart version: ""
install.go:195: [debug] CHART PATH: /home/ubuntu/.cache/helm/repository/ingress-nginx-4.1.4.tgz

client.go:128: [debug] creating 1 resource(s)
client.go:310: [debug] Starting delete for "ingress-nginx-admission" ServiceAccount
client.go:339: [debug] serviceaccounts "ingress-nginx-admission" not found
client.go:128: [debug] creating 1 resource(s)
client.go:310: [debug] Starting delete for "ingress-nginx-admission" ClusterRole
client.go:128: [debug] creating 1 resource(s)
client.go:310: [debug] Starting delete for "ingress-nginx-admission" ClusterRoleBinding
client.go:128: [debug] creating 1 resource(s)
client.go:310: [debug] Starting delete for "ingress-nginx-admission" Role
client.go:339: [debug] roles.rbac.authorization.k8s.io "ingress-nginx-admission" not found
client.go:128: [debug] creating 1 resource(s)
client.go:310: [debug] Starting delete for "ingress-nginx-admission" RoleBinding
client.go:339: [debug] rolebindings.rbac.authorization.k8s.io "ingress-nginx-admission" not found
client.go:128: [debug] creating 1 resource(s)
client.go:310: [debug] Starting delete for "ingress-nginx-admission-create" Job
client.go:339: [debug] jobs.batch "ingress-nginx-admission-create" not found
client.go:128: [debug] creating 1 resource(s)
client.go:540: [debug] Watching for changes to Job ingress-nginx-admission-create with timeout of 5m0s
client.go:568: [debug] Add/Modify event for ingress-nginx-admission-create: ADDED
client.go:607: [debug] ingress-nginx-admission-create: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
client.go:568: [debug] Add/Modify event for ingress-nginx-admission-create: MODIFIED
client.go:607: [debug] ingress-nginx-admission-create: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
Error: INSTALLATION FAILED: failed pre-install: timed out waiting for the condition
helm.go:84: [debug] failed pre-install: timed out waiting for the condition
INSTALLATION FAILED
main.newInstallCmd.func2
	helm.sh/helm/v3/cmd/helm/install.go:127
github.com/spf13/cobra.(*Command).execute
	github.com/spf13/cobra@v1.4.0/command.go:856
github.com/spf13/cobra.(*Command).ExecuteC
	github.com/spf13/cobra@v1.4.0/command.go:974
github.com/spf13/cobra.(*Command).Execute
	github.com/spf13/cobra@v1.4.0/command.go:902
main.main
	helm.sh/helm/v3/cmd/helm/helm.go:83
runtime.main
	runtime/proc.go:255
runtime.goexit
	runtime/asm_amd64.s:1581

Do you have kind or minikube. Please try to install on minikube or kind. But please try 2 versions of K8S i.e v1.23.x and also v1.24.x on minikube or kind. There is #8091 because of which support for v1.24 is flaky.

Thanks, ; Long

On Tue, 14 Jun, 2022, 3:35 PM Kubernetes Prow Robot, < @.***> wrote:

@Divine1 https://github.com/Divine1: This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here https://git.k8s.io/community/contributors/guide/pull-requests.md. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra https://github.com/kubernetes/test-infra/issues/new?title=Prow issue: repository.

— Reply to this email directly, view it on GitHub https://github.com/kubernetes/ingress-nginx/issues/8690#issuecomment-1154981923, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABGZVWRJ2OXMK6ND7MOGKHTVPBKNLANCNFSM5YXDTIOQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

just for the people that may stumble here … i found a workaround for my docker desktop problem … on apple silicon it seems in later versions of docker desktop (4.11+) the installation of the loadbalancer service of nginx can hang, because of not getting an ip or the port beeing blocked this will be indicated by <pending> for the external ip

in this case cleanly uninstall ingress-nginx and stop/start docker desktop again next time the install should work

there is also an old still open issue related to this https://github.com/docker/for-mac/issues/4903

indicating that this is not an ingress-nginx problem … but some trouble with DD on Macos

thanx to @longwuyuan for helping me out on slack

Feeback:

Problem persists with Helm Chart 4.2.3 On Latest Docker Desktop Kubernetes , Apple Silicon

Helm charts hangs with “waiting for condition”. Ingress Controller gets into ready state 1/1 though … but is unusable afterwards

Did anybody verify that the new version is working on Docker Desktop ?

@Divine1 there was a long awaited PR that merged recently. So we would love to get feedback/confirmation. Thank you very much for taking time to update.

@Divine1 if your problem is solved by Chart version 4.2.3 or if no longer relevant, then kindly help and close the issue.

It seems my issue with k8s 1.22 was because I had forgotten to reinstall cillium when downgrading. I have now successfully installed on k8s 1.22.11.