Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get rid of kubernetes-release/archive #3716

Closed
saschagrunert opened this issue Aug 21, 2024 · 6 comments · Fixed by #3717
Closed

Get rid of kubernetes-release/archive #3716

saschagrunert opened this issue Aug 21, 2024 · 6 comments · Fixed by #3717
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@saschagrunert
Copy link
Member

saschagrunert commented Aug 21, 2024

The archives are inherited from anago times, for example: https://console.cloud.google.com/storage/browser/kubernetes-release/archive/anago-v1.31.0

They mainly contain:

  • the build logs (available using GCB)
  • the announcement (can be moved over to kubernetes-release/release/v1.31.0)
  • the release notes html and JSON (not used, because already part of kubernetes-release/release/v1.31.0)
  • the archive k8s.io.tar.gz (probably not needed)

The idea is to move the announcement into the release artifacts (release/v1.y.z) directory and completely avoid collecting the archive. All of that can be done in krel.

cc @kubernetes/release-engineering

@k8s-ci-robot k8s-ci-robot added needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-priority labels Aug 21, 2024
@ameukam
Copy link
Member

ameukam commented Aug 21, 2024

/kind feature
/priority important-longterm

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-priority labels Aug 21, 2024
@ameukam
Copy link
Member

ameukam commented Aug 21, 2024

We should drop the archive k8s.io.tar.gz and the release logs to begin with.

@ameukam
Copy link
Member

ameukam commented Aug 21, 2024

/sig release
/sig k8s-infra

@k8s-ci-robot k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. labels Aug 21, 2024
@saschagrunert
Copy link
Member Author

Starting to work on this in #3717

@BenTheElder
Copy link
Member

the build logs (available using GCB)

I do think this should probably be published publicly? We have a build process that is not fully reproducible.

@saschagrunert
Copy link
Member Author

the build logs (available using GCB)

I do think this should probably be published publicly? We have a build process that is not fully reproducible.

Funnily we just publish the release logs right now, but not the stage ones. I think we have to follow-up on that. I'm not sure what the best way is to deal with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants