sig-release

sig-release copied to clipboard

What would you like to be added:

We need a cohesive story around artifact management.

Broadly, this will cover:

• File artifacts
• Container images
• deb/rpm packages

There are several issues which describe various aspects of developing a process, as well as user feature requests, so to start, we should do some issue collection.

• [x] Create an "Epics" column in the SIG Release project board and add this epic to it
• [x] Create a project board for artifact management: https://github.com/orgs/kubernetes/projects/48
• [x] Add the area/artifacts label to repos which may contain artifact issues/PRs: https://github.com/kubernetes/test-infra/pull/20111
• [x] Scrape the respective repos for artifact issues/PRs and tag w/ area/artifacts
• [x] Add aforementioned issues/PRs to the Artifact Management project board
• [ ] KEP cleanup:
  • [ ] Image Promotion: https://github.com/kubernetes/enhancements/issues/1734
  • [ ] Artifact Management: https://github.com/kubernetes/enhancements/issues/1732
  • [ ] Publishing Packages: https://github.com/kubernetes/enhancements/issues/1731
• [ ] Further populate this list and cross link all artifact issues/PRs to the epic

/assign /milestone v1.21 cc: @kubernetes/sig-release-leads @kubernetes/release-engineering

---

Tasks from https://github.com/kubernetes/k8s.io/issues/170:

• [ ] Design Document describing how all this will work.
• [ ] GCR Repository for official published images
• [ ] GCR Repository for projects to use (https://github.com/kubernetes/k8s.io/issues/158)
• [ ] GCS Bucket for projects to use (https://github.com/kubernetes/k8s.io/issues/153)
• [ ] Process for image promotion (https://github.com/kubernetes/k8s.io/issues/157)
• [ ] ECR Repository mirror for Amazon
• [ ] ACR Repository mirror for Azure
• [ ] HTTP Redirector for image and artifact renaming.

and @spiffxp's notes:

/remove-help I don't think this is appropriately scoped for help wanted

/priority important-longterm Very important for the longterm health of this project. We've migrated image hosting (k8s.gcr.io), but we haven't migrated binary artifact hosting (dl.k8s.io). So we're not all the way done and already hosting/serving artifacts is a very non-trivial amount of our spend We will need to start the conversation back up on mirroring.

Issue covers too much, should break into:

* k8s.gcr.io mirroring
* binary artifact promotion
* artifact mirroring

Can close once those are created

(Tasks from https://github.com/kubernetes/k8s.io/issues/170 moved to epic description.)

More ideas from the Twitterverse: https://twitter.com/pythomit/status/1353794885099245568?s=19

cc: @tpepper

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-contributor-experience at kubernetes/community. /lifecycle stale

/remove-lifecycle stale

/assign @hh Because of :

HTTP Redirector for image and artifact renaming.

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

Tracking issue for file promotion: https://github.com/kubernetes-sigs/k8s-container-image-promoter/issues/413

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

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

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:

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

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

/close

@k8s-triage-robot: Closing this issue.

In response to this:

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:

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

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

/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.

/reopen

@ameukam: Reopened this issue.

In response to this:

/reopen

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.

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:

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

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

/close

@k8s-triage-robot: Closing this issue.

In response to this:

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:

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

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

/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.