Inconsistency during chart installation in namespace

[ronny35]

Terraform, Provider, Kubernetes and Helm Versions

Terraform v1.10.5
on darwin_amd64
+ provider registry.terraform.io/hashicorp/helm v3.0.0-pre1
+ provider registry.terraform.io/hashicorp/kubernetes v2.35.1

Affected Resource(s)

• helm_release

Terraform Configuration Files

resource "helm_release" "release" {
  name       = "wazuh"
  repository = "https://promptlylabs.github.io/wazuh-helm-chart/"
  chart      = "wazuh"
  version    = "0.0.5"
  namespace  = "wazuh"
  create_namespace = true
}

Steps to Reproduce

1. terraform apply

Expected Behavior

Helm chart installed in the correct namespace

Actual Behavior

Chart installed in default namespace, correct namespace is not taken into account

[kiddouk]

Having the same issue here, except that it uses the namespace "terraform", which is a namespace in which I installed another release.

[beiliubei]

same issue.

[lynkz-matt-psaltis]

For us, the chart itself is in the correct namespace however the resources of the chart are arbitrarily installed into the default namespace. Its not every resource of the chart either.

[jrfeenst]

It looks like resources which explicitly specify the namespace field to be {{ .Release.Namespace }} work and end up in the correct place, but if a k8s resource does not specify the namespace it will end up in the default namespace.

[Zerotay]

I had the same issue when usign kube ops view of geekbooks.
With downgrading to 2.17.0 from 3.0.0pre2, the problem solved.
This issue seems happens only with the charts containing sub-charts or library-charts.

[FredM]

The bug is referenced here #1582 and the MR here #1583

[leonardochaia]

Hi, is there any update on this topic? will #1583 get merged eventually or should a fix for this be implemented in some other way?

[jaylonmcshan19-x]

#1583 has been merged, which will tackle this issue!