Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

k8s.helm.v3.Chart does not respect namespace restriction in the provider #1570

Closed
bob-bins opened this issue May 10, 2021 · 1 comment
Closed
Assignees
Labels
area/helm kind/bug Some behavior is incorrect or out of spec mro2 Monica's list of 2st tier overlay related issues resolution/duplicate This issue is a duplicate of another issue

Comments

@bob-bins
Copy link

When the namespace property in k8s.helm.v3.Chart is not specified, even if the provider is restricted to a namespace, the chart will deploy to the default namespace instead of the provider's namespace

Expected behavior

I expect the chart to deploy to the provider's namespace when I don't specify a namespace in the chart.

Current behavior

The helm chart deploys in the default namespace

Steps to reproduce

The following code will deploy to the default namespace. If I uncomment the commented line, it will deploy to namespace ns1

const k8sProvider = new k8s.Provider("k8s", {
  cluster: blahblah,
  namespace: "ns1",
})

const chart = new k8s.helm.v3.Chart(
  "redis",
  {
    chart: "redis",
    // namespace: "ns1",
    version: "14.1.1",
    fetchOpts: {
      repo: "https://charts.bitnami.com/bitnami",
    },
  },
  {
    provider: k8sProvider,
  }
)
@bob-bins bob-bins added the kind/bug Some behavior is incorrect or out of spec label May 10, 2021
@lblackstone lblackstone self-assigned this May 11, 2021
@lblackstone lblackstone added kind/bug Some behavior is incorrect or out of spec and removed kind/bug Some behavior is incorrect or out of spec labels May 11, 2021
@mnlumi mnlumi added the mro2 Monica's list of 2st tier overlay related issues label Mar 28, 2023
@lblackstone lblackstone removed their assignment Jul 14, 2023
@EronWright EronWright self-assigned this Apr 1, 2024
@EronWright EronWright added the resolution/duplicate This issue is a duplicate of another issue label Apr 1, 2024
@EronWright
Copy link
Contributor

Closing as a duplicate of: #1503

@EronWright EronWright closed this as not planned Won't fix, can't repro, duplicate, stale Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/helm kind/bug Some behavior is incorrect or out of spec mro2 Monica's list of 2st tier overlay related issues resolution/duplicate This issue is a duplicate of another issue
Projects
None yet
Development

No branches or pull requests

5 participants