Velero kubernete addon ...manage_via_gitops does not work

[bmacauley]

Description

I cannot install Velero using argocd. It always installs via helm

I am using the following...
argocd_manage_add_ons = true

Other modules are working fine and install via argocd eg externaldns

The velero module is missing this line...

manage_via_gitops = var.manage_via_gitops

Versions

• Module version : v4.14.0

• Terraform version: 1.1.9

[Zvikan]

Hey, if you are referring to using https://github.com/aws-samples/eks-blueprints-add-ons , velero is not there, that's why it's not being installed for you and others.
I'll look into it as I'm already doing some work around the GitOps area now

[Zvikan]

aws-samples/eks-blueprints-add-ons#113 created, once merge feel free to give it another run

[dkravetz]

I'm currently doing a PoC with blueprints, managing add-ons via GitOps and this is still a present problem.

Even when adding locally manage_via_gitops = var.manage_via_gitops to https://github.com/aws-ia/terraform-aws-eks-blueprints/blob/main/modules/kubernetes-addons/velero/main.tf I end up with Velero in both ArgoCD and a Helm release that Terraform tries to apply.

Moreover, I end up with the following error messages, despite the fields being specified, whenever I sync Velero with Argo. If I Sync with Apply Only, there are no issues being reported

[bryantbiggs]

thank you for the issue! At this time we are re-evaluating the integration between Terraform and GitOps operators like ArgoCD. We have removed the integration from the current project and will be tracking all feedback input in #114 while developing the next iteration of this integration