search

kubernetes-retired / spartakus

[EOL] Anonymous Usage Collector
Apache License 2.0
74 stars 30 forks source link

Archive this project #38

Closed fejta closed 4 years ago

fejta commented 5 years ago

It does not appear like we are doing much with this data. Let's turn it down in the utility cluster and archive this project.

/assign @fejta @thockin

aronchick commented 5 years ago

Well, FWIW, Kubeflow uses this very heavily.

/cc @jlewi

fejta commented 5 years ago

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

So this is two things we want to stop supporting:

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

thockin commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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

thockin commented 5 years ago

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 notifications@github.com 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 https://github.com/kubernetes-incubator/spartakus/issues/38#issuecomment-465260350, or mute the thread https://github.com/notifications/unsubscribe-auth/AFVgVFK0Wzp-N-MTXCVcWrtLwp3vurK0ks5vPEangaJpZM4axw6S .

fejta-bot commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 4 years ago

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 commented 4 years ago

@fejta-bot: Closing this issue.

In response to [this](https://github.com/kubernetes-incubator/spartakus/issues/38#issuecomment-514297439): >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](https://github.com/fejta). >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.