#help - June 2024

Hi team,
I need to deploy all of our microservices in Kubernetes using Helm. Currently, I go to each project, run helm create <project-name>, modify some deployment templates, and then install the app with that Helm package. Could anyone suggest best practices for managing Helm charts for all of our microservices?

Additionally, I have another idea for managing our Helm charts. We could create a separate GitLab group for all our Helm charts and set up CI/CD pipelines to automatically create or update Helm charts based on any modifications. These would then be pushed to a private Helm repository. During deployment, we could fetch the latest version of the Helm chart from the private repo.
What do you think?

Thanks!

Hello, I am trying to create module `_module_ "pdf_ecs_task" {
source = "cloudposse/ecs-alb-service-task/aws"
_version_ = "0.66.4" with task_policy_arns = [
module.pdf_ecs_iam_policy.policy_arn
] but got this error: Error: Invalid for_each argument
│
│ on .terraform/modules/pdf_ecs_task/main.tf line 162, in resource "aws_iam_role_policy_attachment" "ecs_task":
│ 162: for_each = local.create_task_role ? toset(var.task_policy_arns) : toset([])
│ ├────────────────
│ │ local.create_task_role is true
│ │ var.task_policy_arns is list of string with 1 element`

Not sure where to post this but it seems like there was a delete button or the docs were moved from the modules page in the documentation here: https://docs.cloudposse.com/modules/