Archive this project

[fejta]

Archive this project

[aronchick]

Well, FWIW, Kubeflow uses this very heavily.

/cc @jlewi

[fejta]

Note that the last PR was March 2018, last closed issue was April 2017.

So this is two things we want to stop supporting:

• the instance in the kubernetes community utility cluster
• the codebase

I assume kubeflow is running their own instance? If they need this then how about we move the repo into the kubeflow org?

[thockin]

I have had a couple nibbles about restarting the work. I don't want to nuke this just yet, but we can turn down the current instance that is running, at least.

[squat]

Likewise, I’ve had quite some ideas about potential for reinvesting in this project especially given some of the overlap and lessons learned from working on telemetry for OpenShift.

[jlewi]

Kubeflow is running its own instance of spartakus so we don't depend on the test cluster that @fejta wants to shutdown.

[thockin]

I scaled the collector to 0 - should have no detrimental impact on anyone running the volunteer.

…

On Tue, Feb 19, 2019 at 10:47 AM Jeremy Lewi ***@***.***> wrote: Kubeflow is running its own instance of spartakus so we don't depend on the test cluster that @fejta <https://github.com/fejta> wants to shutdown. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#38 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFVgVFK0Wzp-N-MTXCVcWrtLwp3vurK0ks5vPEangaJpZM4axw6S> .

[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

[brianredbeard]

Speaking of this, if most instances have been scaled to 0, possibly this is a good opportunity to retool #29 (Intention of Timestamp structure).

Thoughts?

[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-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.