I had some strange issues with traffic/connections, let me describe my issue below: I have AWS EKS + configured "aws-load-balancer-controller". I have several pods + ingress (when ingress is going to be added to EKS - ALB was successfully created…
we have an EKS cluster on 1.21. There is an nginx-ingress-controller-default-ingress-controller deployed with a Classic Load Balancer. Suddenly, its pods are crashing with following errors. I0815 04:40:04.970835 8 flags.go:204] Watching for Ingress class: nginx W0815 04:40:04.980149 8 flags.go:249] SSL certificate…
I am trying to deploy EKS Cluster using terraform. Currently I am using source as "hashicorp/aws" and version: 5.16.0, I am trying to deploy in "il-central-1" region. I am getting error as "Invalid AWS Region: il-central-1". This is my provider…
One of the steps to log into ECR required to pull and push images is the following, according to AWS (https://docs.aws.amazon.com/AmazonECR/latest/userguide/getting-started-cli.html): aws ecr get-login-password --region region | docker login --username AWS --password-stdin aws_account_id.dkr.ecr.region.amazonaws.com However, from starting from Kubernetes v1.24, Docker…
When I try to get the secrets by running the microservice on my machine it brings them up without problems, but when I dockerize the environment and run the microservice inside the container it gives me the following error: CredentialsProviderError:…
I normally use GKE but wanted to test EKS and I am struggling to deploy nginx as ingress-controller. In GKE I get an external IP, put it in the values config (controller.service.loadBalancerIP) sent it and ready to go. In AWS…
I am seeing the following error: Failed to parse host: parse "https://"https://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.xx.us-east-1.eks.amazonaws.com"n": net/url: invalid control character in URL, while performing terraform apply All I was trying to do is to use a null resource, to execute eks command, and output…
I am trying to use oauth-proxy to provide authentication on the kubernetes dashboard using keycloak in EKS. I have managed to get to a point where oauth-proxy will forward the authorization header to the dashboard, however I am getting 'unauthorized'…
What is the relationship between the role my principal is using and the RBAC in k8s? Specifically, when I do kubectl describe -n kube-system configmap/aws-auth I see this role: myAmazonEKSNodeRole as described here. But when I look in the role…
I have an EKS cluster. When I deploy my container it fails to start with the following message: Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container…