Skip to content
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

[Bug]: Cannot use tofu apply to create terraform resources "as-is" #199

Open
1 task done
ucfchandra opened this issue Jun 10, 2024 · 1 comment
Open
1 task done
Labels
bug Something isn't working

Comments

@ucfchandra
Copy link

ucfchandra commented Jun 10, 2024

Welcome to AWS Blueprints for Crossplane!

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

AWS Blueprints for Crossplane Release version

First release

What is your environment, configuration and the example used?

Mac OS, example was the terraform bootstrap

What did you do and What did you see instead?

I attempted Tofu apply and got the following errors:

Warning: Helm release "argo-cd" was created but has a failed status. Use the `helm` command to investigate the error, correct it, then run Terraform again.
│ 
│   with module.eks_blueprints_addons.module.argocd.helm_release.this[0],
│   on .terraform/modules/eks_blueprints_addons.argocd/main.tf line 9, in resource "helm_release" "this":
│    9: resource "helm_release" "this" {
│ 
╵
╷
│ Error: failed to create resource: Internal error occurred: failed calling webhook "mservice.elbv2.k8s.aws": failed to call webhook: Post "https://aws-load-balancer-webhook-service.kube-system.svc:443/mutate-v1-service?timeout=10s": no endpoints available for service "aws-load-balancer-webhook-service"
│ 
│   with module.eks_blueprints_addons.module.argocd.helm_release.this[0],
│   on .terraform/modules/eks_blueprints_addons.argocd/main.tf line 9, in resource "helm_release" "this":
│    9: resource "helm_release" "this" {

Additional Information

I was able to successfully work around this issue by changing `wait = true` to `wait = false` in the EKS Addons section under `argocd`
@ucfchandra ucfchandra added the bug Something isn't working label Jun 10, 2024
@edgarsilva948
Copy link
Collaborator

Hello @ucfchandra,

Thank you for bringing this!

It looks like the problem arises due to ArgoCD Helm installation being initiated before all cluster addons are fully operational. To address this, I've made some adjustments in this PR.

I've added this parameter to the VPC-CNI addon to ensure that it fully initializes before we attempt the ArgoCD Helm install. Additionally, I've added a sleep time to provide a buffer and ensure that everything is up and running. These changes should resolve the timing issue and prevent the errors you encountered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants