fix(kubeconfig): Enforces kubernetes context with helm release namespace

[flavioab]

Description

Overriding Kubernetes context default namespace with helm release namespace.

Acceptance tests

• Have you added an acceptance test for the functionality being added?

Release Note

Release note for CHANGELOG:

Fix for dependency charts installed in non-default namespaces

References

#1582 #1591

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[hashicorp-cla-app]

All committers have signed the CLA.

[JaylonmcShan03]

Hey @flavioab 👋 thanks for the fix—it makes sense to explicitly enforce the namespace override here, especially for charts with dependencies.

To help us ensure we don’t regress this behavior in the future, would you mind adding an acceptance test that reproduces the issue and validates that dependency resources get installed in the correct namespace?

Let me know if you need help mocking up a test case—happy to help!

[flavioab]

Hi @JaylonmcShan03 , finally an update on this 🙌 . I will try to increment the acceptance tests this weekend, thought about adding it before, but badly knew if this PR would be considered at some point.

[flavioab]

@JaylonmcShan03 , acceptance tests are in place. Please feel free to make any changes on this if necessary. This test will iterate over all resources from the release and assert if the namespace is correct.

[flavioab]

@JaylonmcShan03, are there any updates? Please let me know if you still need assistance with this PR.

[JaylonmcShan03]

Hi, @flavioab Just reviewed and the changes introduced looks spot on! Can you rebase this pr onto the current main?

[aldegoeij]

Hi, @flavioab Just reviewed and the changes introduced looks spot on! Can you rebase this pr onto the current main?

@flavioab 💘

[cradules]

Any updates? This is affecting us quite badly and I can't find a workaround!

Example:
resource "helm_release" "flux" {
name = "flux"
namespace = var.flux_namespace
repository = "https://fluxcd-community.github.io/helm-charts"
chart = "flux2"
version = var.flux_version
create_namespace = true
set = [
{
name = "installCRDs"
value = "true"
}
]
}

where var.flux_namespace = flux-system.

The helm is created on flux-system but the rests of the objects on default namespace!

[flavioab]

Hi @cradules , been checking on this once per week since Feb..... been a really slow process overall

[jaylonmcshan19-x]

Hi @flavioab Sorry for the late response! Can you please add a changelog entry! Once that is tackled, I can approve :)

No longer have access to the account