Skip to content
This repository has been archived by the owner on Mar 26, 2021. It is now read-only.

Support grouping of clusters #81

Closed
perotinus opened this issue Nov 16, 2017 · 2 comments
Closed

Support grouping of clusters #81

perotinus opened this issue Nov 16, 2017 · 2 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster.
Milestone

Comments

@perotinus
Copy link
Contributor

/sig multicluster

This is mainly to support authorization on groups of clusters. Namespaces are the obvious mechanism for this, but they are not the only one and we need to do some design work here to find the right approach.

From https://github.com/kubernetes/community/blob/master/contributors/design-proposals/multicluster/cluster-registry/project-design-and-plan.md#beta

@k8s-ci-robot k8s-ci-robot added the sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster. label Nov 16, 2017
@perotinus perotinus added this to the v0.2 (Beta) milestone Nov 16, 2017
@perotinus
Copy link
Contributor Author

There is some more discussion about this in this doc.

@perotinus perotinus mentioned this issue Feb 2, 2018
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster.
Projects
None yet
Development

No branches or pull requests

3 participants