Can't Add Namespace Rights On Same Project

[estein9825]

Expected vs actual behavior

In the UI, if you grant namespace rights against a project, it no longer is choosable as a option if you want to grant other namespace rights for different namespaces. In otherwords, I might want admin rights against the monitoring and platform namesapce in the test project, and read only rights on the kube-system and prometheus namespace. That is not possible through the UI. This is most likely a limitation brought on by #172

Steps to reproduce the bug

1. Create a project
2. Attempt to grant it rights against a project for specific namespaces
3. Attempt to grant it rights for a different project

Are you using the latest version of the project?

You can check your version by running helm ls|grep '^<deployment-name>' or using pctl, pctl version, and provide the output.

VERSION: 0.1.0
BUILD: 0.1.0
BUILD-TIME: 1656329967
ARCH: darwin/amd64

What is your environment setup? Please tell us your cloud provider, operating system, and include the output of kubectl version --output=yaml and helm version. Any other information that you have, eg. logs and custom values, is highly appreciated!

Kubectl

clientVersion:
  buildDate: "2022-08-23T17:44:59Z"
  compiler: gc
  gitCommit: a866cbe2e5bbaa01cfd5e969aa3e033f3282a8a2
  gitTreeState: clean
  gitVersion: v1.25.0
  goVersion: go1.19
  major: "1"
  minor: "25"
  platform: darwin/amd64
kustomizeVersion: v4.5.7
serverVersion:
  buildDate: "2022-11-29T18:41:42Z"
  compiler: gc
  gitCommit: 52e500d139bdef42fbc4540c357f0565c7867a81
  gitTreeState: clean
  gitVersion: v1.22.16-eks-ffeb93d
  goVersion: go1.16.15
  major: "1"
  minor: 22+
  platform: linux/amd64

Helm

version.BuildInfo{Version:"v3.10.3", GitCommit:"835b7334cfe2e5e27870ab3ed4135f136eecc704", GitTreeState:"clean", GoVersion:"go1.19.4"}

(optional) If you have ideas on why the bug happens or how it can be solved, please provide it here

The current workaround is to use the API. Which means there is an issue with the UI.

• [X ] I've described the bug, included steps to reproduce it, and included my environment setup with all customizations.
• [ X] I'm using the latest version of the project.

[akshay196]

Tested group role association with different projects using API. It worked.

  "spec": {
    "projectNamespaceRoles": [
      {
        "project": "default",
        "namespace": "monitoring",
        "role": "NAMESPACE_ADMIN",
        "group": "mygroup"
      },
      {
        "project": "default",
        "namespace": "platform",
        "role": "NAMESPACE_ADMIN",
        "group": "mygroup"
      },
      {
        "project": "default",
        "role": "NAMESPACE_READ_ONLY",
        "namespace": "kube-system",
        "group": "mygroup"
      },
      {
        "project": "default",
        "role": "NAMESPACE_READ_ONLY",
        "namespace": "prometheus",
        "group": "mygroup"
      }

Looks like UI need to tweaked to support associating multiple roles with same project.