aws-ia / terraform-aws-eks-blueprints

Configure and deploy complete EKS clusters.
https://aws-ia.github.io/terraform-aws-eks-blueprints/
Apache License 2.0
2.72k stars 1.43k forks source link

strimzi-kafka-operator: Namespace not created when `argocd_manage_add_ons=true` #1309

Closed Sebelino closed 1 year ago

Sebelino commented 1 year ago

Description

I am trying to use strimzi-kafka-operator by setting enable_strimzi_kafka_operator = true in a module call to kubernetes-addons. However, when ArgoCD is managing the add-ons, ArgoCD fails to sync because a Kubernetes namespace for Strimzi is not being created.

image

Versions

Reproduction Code [Required]

Add enable_strimzi_kafka_operator = true to the examples/gitops/argocd/ example:

https://github.com/aws-ia/terraform-aws-eks-blueprints/blob/a91b8409eac7442323de800584e762a525cde268/examples/gitops/argocd/main.tf#L126

Steps to reproduce the behavior:

  1. cd examples/gitops/argocd
  2. Add enable_strimzi_kafka_operator = true to the eks_blueprints_kubernetes_addons module call
  3. terraform init
  4. terraform apply

Expected behaviour

A Kubernetes namespace named strimzi is created.

Actual behaviour

A Kubernetes namespace named strimzi is not created.

Terminal Output Screenshot(s)

Additional context

bryantbiggs commented 1 year ago

this should be solved on the chart for the operator instead, like this https://github.com/aws-samples/eks-blueprints-add-ons/blob/1b131cafc5a331cf32d7d269fc8aa3ded69a803c/chart/templates/vault.yaml#L24-L25