Skip to content

gateway.attachedNamespaces allowlists cozy-linstor-gui, but linstor-gui installs into cozy-linstor #4105

Open

Description

The Gateway attached-namespaces allowlist in packages/core/platform/values.yaml contains cozy-linstor-gui. No such namespace exists: packages/core/platform/sources/linstor-gui.yaml installs the chart into cozy-linstor, the same namespace as linstor and linstor-scheduler.

Nothing is broken today, and that is what makes it worth filing rather than leaving. The allowlist decides which namespaces may attach routes to the tenant Gateway. linstor-gui currently ships no route, so an entry naming a namespace that does not exist has no observable effect. The day the chart grows an HTTPRoute, it will land in cozy-linstor and fail to attach, and the allowlist will look correct to whoever reads it, because the entry is right there with the expected name.

The same wrong namespace is repeated in the chart is own ingress wildcard test, so a reader checking the test for confirmation gets the error twice and reads it as agreement.

Fix is one word in the allowlist plus the test, and worth doing before the route exists rather than after someone spends an afternoon on why it does not attach. Worth checking the rest of that list at the same time: an entry can only be verified against where a chart actually installs, and nothing in the tree ties the two together.

Activity

  1. added
    kind/bugCategorizes issue or PR as related to a bug
    area/networkingIssues or PRs related to networking (ingress, gateway, vpn, metallb, kube-ovn)
    triage/acceptedIndicates an issue is ready to be actively worked on
    priority/backlogGeneral backlog priority. Lower than priority/important-longterm
    and removed
    triage/needs-triageIndicates an issue needs triage by a maintainer
    on Sep 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/networkingIssues or PRs related to networking (ingress, gateway, vpn, metallb, kube-ovn)kind/bugCategorizes issue or PR as related to a bugpriority/backlogGeneral backlog priority. Lower than priority/important-longtermtriage/acceptedIndicates an issue is ready to be actively worked on

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions