-
Notifications
You must be signed in to change notification settings - Fork 140
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
ingress nginx and cert manager timeout issue - K8s 1.22 #359
Comments
no configs changed, I'm using the same file from this repo except the aws/helm versions are changed |
Have the same problem, did you find a solution? Edit: I resolved the issue by increasing instance resources. |
@theraaz can you list the pods in your cluster and post it here? When Helm is the state of creating...it is usually waiting for all of the pods it just launched to come to a kubernetes ready state. One of your pod might not be in a ready state for a number of reasons. @rezaav said above he increased instance resources which allowed the pod to be created which then the terraform helm deployment finished. It could be the same problem on your cluster or another. Listing the pods is the first troubleshooting step. Then it is probably describing the pod that is in some none ready state. |
Any updates on this how did you resolve it ? I'm using source = "github.com/ManagedKube/kubernetes-ops//terraform-modules/aws/helm/helm_generic?ref=v2.0.82" and increased timeout to 3600 and still
|
Hi, I tried to upgrade EKS Kubernetes to 1.22. Auto scaler and cert manager were timing out but after updating the versions of
aws
andhelm
terraform providers to latest versions and changing the api version link from alpha to beta, it started workingNow i'm stuck with the Nginx ingress. Possibly because of the Nginx announced changes
here is the error I receive
any suggestions? if it is just changing the api version, how can I do that?
The text was updated successfully, but these errors were encountered: