Does CentralUi need ClusterScope?

[jlewi]

See #1213

We'd like to be able to scope Kubeflow to a particular namespace to better support multi-tenant environments.

It looks like CentralUI is creating a ClusterRole right now. Do we need ClusterScope? Could we use a namespace scoped role?

/cc @swiftdiaries

[swiftdiaries]

If Kubeflow components (Argo, job-operator, jupyter, Katib) are deployed to same namespace then CentralUI doesn't need ClusterScope. A namespaced scope should be good enough.

[jbottum]

/area 0.4.0

[jbottum]

/remove-area 0.4.0

[jlewi]

@swiftdiaries Until proven otherwise, I think we can assume central dashboard is in the same name space as the other components.

So lets replace the cluster scoped role with a namespace scoped role.

[swiftdiaries]

Sounds good 👍 Will get a PR in with the change.

…

On Sun, Oct 7, 2018 at 20:05 Jeremy Lewi ***@***.***> wrote: @swiftdiaries <https://github.com/swiftdiaries> Until proven otherwise, I think we can assume central dashboard is in the same name space as the other components. So lets replace the cluster scoped role with a namespace scoped role. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1450 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AV9Rn2-ZAWk2AR0CNRIXCwV9cxiNqiAiks5uisEMgaJpZM4WVRbQ> .

[chrisheecho]

/remove-priority p1
/priority p0

[swiftdiaries]

Closing because a PR has already been submitted and merged for this.
/close

[k8s-ci-robot]

@swiftdiaries: Closing this issue.

In response to this:

Closing because a PR has already been submitted and merged for this.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.