sig-release icon indicating copy to clipboard operation
sig-release copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

Define and collect output metrics about Kubernetes releases

Open saschagrunert opened this issue 3 years ago • 10 comments

Counterpart to https://github.com/kubernetes/sig-release/issues/1527.

It would be very useful to obtain additionally output usage metrics of Kubernetes releases, for example the download counts of different artifacts during specific time spans. Target of this issue is to define the metrics, whereas the actual implementation can be done as follow-up in dedicated issues.

saschagrunert avatar Oct 08 '21 07:10 saschagrunert

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Jan 06 '22 08:01 k8s-triage-robot

/remove-lifecycle stale

saschagrunert avatar Jan 10 '22 09:01 saschagrunert

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Apr 10 '22 10:04 k8s-triage-robot

/remove-lifecycle stale

saschagrunert avatar Apr 11 '22 07:04 saschagrunert

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Jul 10 '22 07:07 k8s-triage-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot avatar Aug 09 '22 08:08 k8s-triage-robot

I think we can start working on this by trying to find out if we can collect the stats from the GCS buckets for the binary artifacts, container images as well as packages.

@kubernetes/release-managers is someone interested in working on this?

saschagrunert avatar Sep 07 '22 07:09 saschagrunert

As per discussion in https://kubernetes.slack.com/archives/CJH2GBF7Y/p1662539543468499?thread_ts=1662537592.107829&cid=CJH2GBF7Y:

There are currently multiple infrastructure changes ongoing in parallel:

  • GCR to AR : https://github.com/kubernetes/k8s.io/issues/1343
  • deb/rpm to OBS | GCS : https://github.com/kubernetes/release/issues/913
  • binaries from Google infra to community Infrastructure : https://github.com/kubernetes/k8s.io/issues/2396

This means we should finish those big changes before we take a look into this. It’s gonna be easier for us to get those metrics once we finish the migration.

saschagrunert avatar Sep 07 '22 08:09 saschagrunert

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Feb 08 '23 02:02 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Feb 08 '23 10:02 xmudrii