Kubernetes/cluster-registry appears to be abandoned

[chases2]

Organization or repository

kubernetes/cluster-registry

Describe the issue

The repository hasn't been modified since March 13th. Issues in the repository are currently rotting away. Consider archiving this repository?

[cblecker]

/assign @pmorie @quinton-hoole
/sig multicluster
Assigning sig-multicluster chairs

[nikhita]

@pmorie @quinton-hoole friendly ping :)

[nikhita]

@pmorie @quinton-hoole Can you take a look at this?

[cblecker]

sent an e-mail to the sig list

[pmorie]

We discussed this in our May 26 meeting. The predominant sentiment seemed to be that the project is essentially defunct in its present form. It is possible that we will create something similar in the future, but the SIG does not want to be bound by prior decisions made in this repo. It is also likely that we will create any new repository for this in the kubernetes-sigs github org. I will send a message to the mailing list so that we can have a lazy consensus to archive this project.

[nikhita]

@pmorie 👋 Just following up. Has there been a date set for the lazy consensus already? Couldn't find one the mailing list.

[RainbowMango]

I don't think this repo should be archived, in addition, I've some idea about how this API should be enhanced. Please just wait for a while, we will discuss it at the SIG meeting.

[k82cn]

@pmorie , any conclusion there? we'd like to use this report as cluster-api for multi-cluster scenario.

xref: volcano-sh/volcano#880

[nikhita]

@k82cn @RainbowMango I'd recommend following up on the mailing list, github notifications can sometimes go to a black hole 🙃

[k82cn]

sure, thanks very much for your reminder :)

[pmorie]

Thanks for bumping, I see @RainbowMango's reply now.

If there's an objection, we should give this some additional discussion time in a SIG meeting. I have put an item on July 07, 2020 agenda to discuss. We will set a date for lazy consensus at that time.

[pmorie]

We have deferred a decision on whether the existing repository will be archived or not; currently collecting use cases for a future cluster registry concept in the community in a world-writable doc. More information here. Anyone should feel welcome to add to this document; we'll discuss use-cases in coming SIG meetings. We'll provide notice when there is a 'last call' for use cases.

[fejta-bot]

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

[nikhita]

/remove-lifecycle stale

@pmorie has a decision been taken already?

[fejta-bot]

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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[nikhita]

/lifecycle frozen

…

On Sat, Feb 6, 2021 at 10:44 AM fejta-bot ***@***.***> wrote: Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close. Send feedback to sig-contributor-experience at kubernetes/community <https://github.com/kubernetes/community>. /lifecycle rotten — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1499 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD24BUBECWABURND3VHDZ63S5TF4JANCNFSM4J5RNEMA> .

[mrbobbytables]

@pmorie do you know if a decision was reached? It's been some time now and the repo's still most recent activity is from 2+ years ago.

[nikhita]

Going ahead with the archival based kubernetes/community#5661

[nikhita]

Repo has been archived: https://github.com/kubernetes-retired/cluster-registry

Also sent a notice to the multicluster mailing list + k-dev - https://groups.google.com/g/kubernetes-dev/c/FaxRtx2t0nw

The following PRs should merge before this issue can be closed:

• Remove GitHub teams for cluster-registry #2602 - remove GitHub teams
• Remove retired subprojects from SIG MC community#5661 - remove repo from sigs.yaml

[nikhita]

All related PRs have merged, closing