---------------------- This behavior could be related to the use of Garden variables in your Helm chart values. As per a Github issue (), it was observed that Helm charts tend to redeploy when Garden variables are used as values in the Helm chart. If you have static values in the Helm chart, there's no redeployment. Here's an example of a Helm chart that causes redeployment due to the use of Garden variables:

yaml
kind: Module
description: In-cluster PostgreSQL for Keycloak
disabled: ${var.keycloak.database.rds} # if rds is enabled, see infrastructure-aws
type: helm
name: keycloak-pg
chartPath: ./postgresql
dependencies: 
  - infrastructure-aws
values:
  architecture: 'standalone'
  auth:
    database: ${var.keycloak.database.name}
    username: ${var.keycloak.database.username}
    password: "${runtime.services.infrastructure-aws.outputs.keycloak_db_password}"

In contrast, a Helm chart with static values doesn't cause redeployment:

yaml
kind: Module
description: In-cluster Redis for glx-connect
type: helm
name: redis
chartPath: ./redis
values:
  architecture: 'standalone'
  auth:
    enabled: false
  master:
    resources:
      limits:
        cpu: 500m
        memory: 256Mi
      requests:
        cpu: 50m
        memory: 128Mi

If this doesn't solve your issue, it might be worth checking if there are any open issues or bugs related to your specific scenario in the Garden's Github repository. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted