Skip to content

Setting namespaces.nexusNs.enabled to false behaves unexpectedly #130

Description

@SB-MFJ

The chart requires ownership of the namespace by the helm chart.
It also deletes the namespace after uninstalling the helm chart.

Reproduce:

  • Create a namespace
  • set:
    • "namespaces.nexusNs.enabled" = "false"
    • "namespaces.nexusNs.name" = "<your namespace>"
  • install chart

Error:

Unable to continue with install: Namespace "<helm-namespace>" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "nexus"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "<helm-namespace>"

I was expecting that the namespace specified could be created standalone and only the resources created within would be removed after the chart is removed, as opposed to the entire namespace being removed.

Maybe I'm misunderstanding the docs:

Whether a namespace should be created for the Kubernetes resources needed Nexus Repository pod(s)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions