Charles-Edouard Brétéché

I made a step in this direction here: https://github.com/tektoncd/experimental/pull/536 Pipelines don't need to be deployed in each namespace, a single instance of pipelines should be ok. On the other hand,...

@a-roberts yep I heard that ;) We can still use ClusterRole but use RoleBinding instead of ClusterRoleBinding.

I wouldn’t create the roles programmatically, it would require the backend to have permissions to create roles, I would prefer to avoid that for security reasons.

> Doesn't ClusterRole require cluster-admin permissions to install? I think it's like other resources, RBAC decides if one is allowed or not to operate ClusterRoles. Anyway i don't think the...

Issue https://github.com/tektoncd/dashboard/issues/1355 is not related, it's a breaking change in Deployment label selectors (those are immutable). I wrote it in the description of the PR (https://github.com/tektoncd/dashboard/pull/1327) > This will introduce...

I guess we’re talking about strong isolation here, not just ui presentation, otherwise the drop down in the side nav would be enough 😄 Such a setup will probably require...

> 2 is related to providing non-admin users access to the dashboard without giving them cluster-wide access Do you mean preventing them from creating resources in any namespace of the...

> The goal is the ops provision the dashboards (1 per namespace, 1 namespace per team). Then each team have access to its own dashboard showing its own pipelines. Ok...

There are still some details to be worked on but it should be pretty straight forward. My recommended setup would be as follows: - create the tekton-pipelines namespace and install...

> How would you bind a dashboard instance to a specific namespace ? Something along those lines `dashboard --tenant-namespace team1`, it's not currently supported but it's the idea. Regarding your...