You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this a BUG REPORT or FEATURE REQUEST?: FEATURE REQUEST
What happened: Can't deploy px-central twice within the same cluster even within different namespace.
What you expected to happen: expect to be able to run more than 1 helm release, while the 1st helm release keep intact ( no yaml override)
How to reproduce it (as minimally and precisely as possible): create 2 namespaces , deploy px-central helm chart in every namespace , check clusterrolebinding created then overriden
Anything else we need to know?: N/A
Environment: N/A
Container Orchestrator and version:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:
The text was updated successfully, but these errors were encountered:
abdennour
added a commit
to ElmCompany/portworx-helm
that referenced
this issue
Nov 5, 2024
Is this a BUG REPORT or FEATURE REQUEST?: FEATURE REQUEST
What happened: Can't deploy px-central twice within the same cluster even within different namespace.
What you expected to happen: expect to be able to run more than 1 helm release, while the 1st helm release keep intact ( no yaml override)
How to reproduce it (as minimally and precisely as possible): create 2 namespaces , deploy px-central helm chart in every namespace , check clusterrolebinding created then overriden
Anything else we need to know?: N/A
Environment: N/A
uname -a
):The text was updated successfully, but these errors were encountered: