-
Notifications
You must be signed in to change notification settings - Fork 101
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
Deployment problem #66
Comments
hey @Pfriasf - can you check that your
|
Yes, i did but does not work |
Please, what terraform version are you using? If you can, post here your Also, you might want to try Links that might be useful to you: |
Thank you for the quick response, I have tried with the links you suggest but I haven't succeeded either. versions
I will share the file below:
|
The only thing I see differently by comparing your file with the one from our development cluster is that your EKS version is different (ours is 3.53.0 and yours is 3.54.0). It can or cannot be related to your issue, so I would ask you to try fixing the version to 3.53.0 and running |
The problem has been solved, I have performed several actions: I have fixed the versions as you suggested, I have also modified the terraform backend, I was using the remote mode and I migrated it to s3 as you do in the tutorial. |
Hello,
I have a problem following the steps in the tutorial, during the first terraform apply in the creation of the resource : module.mlops-architecture-eks.helm_release.autoscaler I always get the following error:
│ Error: Post "http://localhost/api/v1/namespaces/kube-system/configmaps": dial tcp 127.0.0.1.1:80: connect: connection refused.
│
│ with module.mlops-architecture-eks.module.eks.kubernetes_config_map.aws_auth[0],
│ on .terraform/modules/mlops-architecture-eks.eks/aws_auth.tf line 63, in resource "kubernetes_config_map" "aws_auth":
│ 63: resource "kubernetes_config_map" "aws_auth" {.
│
╵
The text was updated successfully, but these errors were encountered: