Closed akash123-eng closed 1 year ago
This was fixed after adding ephemeral port range in node/worker security group ingress
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Yesterday i upgraded our terraform eks module version from v17.20.0 to v18.26.6 then followed steps given on https://github.com/clowdhaus/eks-v17-v18-migrate for migration and then did terraform apply after which new nodes were created with required IAM policies and all also kube-proxy add on was enabled on exising eks cluster which was our main requirement after that i deleted old nodes which caused all workload to move on to new nodes.. but now when i try to create a new pod or deployment its failing with error Error from server (Timeout): Timeout: request did not complete within requested timeout - context deadline exceeded Initially i thought this may be due to resource cruch so i increased nodes for that but even that didn't solved the issue.
I am able to get details from any pods of the cluster also able to edit the config of resources in the cluster but new pods are not being created and failing with above error Error from server (Timeout): Timeout: request did not complete within requested timeout - context deadline exceeded
please give inputs what could be wrong in this. our kubernetes version in 1.22 PFB below my terraform manifest files for eks.
main.tf
provider.tf