Skip to content

Sharding not possible across namespaces #188

@drewwells

Description

@drewwells

Describe the bug a clear and concise description of what the bug is.

Cluster resources for RBAC are created with static names, but references namespace specific resources. Given a situation where I install flux into two namespaces a and b. The clusterrolebinding mentions the a/serviceaccount. When I go to install b it attempts to create the same clusterrolebinding but mentions b/serviceaccount.

The simple fix is to include the release name in all cluster wide rbac objects.

What's your helm version?

n/a

What's your kubectl version?

n/a

What's the chart version?

2.9.2

What happened?

No response

What you expected to happen?

No response

How to reproduce it?

Install the chart twice in the same cluster into two separate namespaces.

Enter the changed values of values.yaml?

No response

Enter the command that you execute and failing/misfunctioning.

helm install ... normal steps.

Anything else we need to know?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions