crossplane-on-eks icon indicating copy to clipboard operation
crossplane-on-eks copied to clipboard

[Bug]: Kubernetes cluster unreachable

Open leofvo opened this issue 2 years ago • 1 comments

Welcome to AWS Blueprints for Crossplane!

  • [X] Yes, I've searched similar issues on GitHub and didn't find any.

AWS Blueprints for Crossplane Release version

v0.1.0

What is your environment, configuration and the example used?

Using terraform boostrap. Default configuration.

What did you do and What did you see instead?

I'm trying to setup the stack to try it. I run the following command:

terraform init
terraform apply
# The error occur a first time after this command
aws eks --region eu-west-1 update-kubeconfig --name crossplane-blueprints --alias crossplane-blueprints
terraform apply
# error occur again

image

Also, I tried to manually access the cluster, and it seems to be unreachable: image

It's seems to be a problem in the cluster config right ? Any ideas ?

Additional Information

No response

leofvo avatar Mar 05 '24 11:03 leofvo

Hi @LeoFVO,

Check if your cluster was created in eu-west-1 region. The default region is us-east-1: https://github.com/awslabs/crossplane-on-eks/blob/7b77a32d5128de1277114c0ee759423cb90d1da9/bootstrap/terraform/variables.tf#L4-L8 Check if you have AWS_REGION env vars set.

Hope that helps, Christina

candonov avatar Mar 29 '24 09:03 candonov

I had a smilier issue as I was using a profile for my AWS provider to resolve I add a profile argument to the helm provider: args = ["eks", "get-token", "--cluster-name", local.name, "--region", var.region, "--profile", "myawsprofile"]

eddavies-BV avatar Apr 12 '24 13:04 eddavies-BV

I cannot reproduce on my side, if it is still an issue please re-open and provide more details.

candonov avatar May 09 '24 20:05 candonov