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

Migrate away from Google project kubernetes-release-test #3425

Open
3 tasks
ameukam opened this issue Jan 22, 2024 · 9 comments
Open
3 tasks

Migrate away from Google project kubernetes-release-test #3425

ameukam opened this issue Jan 22, 2024 · 9 comments
Assignees
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. 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

@ameukam
Copy link
Member

ameukam commented Jan 22, 2024

The official releases and patch releases are currently done use a Google project where GCB builds are triggered. We should migrate to a community-owned project (preferably k8s-release).

  • Migrate/rotate credentials needed for the release process
  • Create/Replace GCP Service Accounts needed for the release process
  • Create IAM bindings needed for the release process

/sig k8s-infra
/area infra/gcp
/priority important-soon
/milestone v1.30

@ameukam ameukam added kind/feature Categorizes issue or PR as related to a new feature. sig/release Categorizes an issue or PR as relevant to SIG Release. area/release-eng Issues or PRs related to the Release Engineering subproject labels Jan 22, 2024
@k8s-ci-robot
Copy link
Contributor

@ameukam: The provided milestone is not valid for this repository. Milestones in this repository: [next, v1.25, v1.26, v1.27, v1.28, v1.29]

Use /milestone clear to clear the milestone.

In response to this:

The official releases and patch releases are currently done use a Google project where GCB builds are triggered. We should migrate to a community-owned project (preferably k8s-release).

  • Migrate/rotate credentials needed for the release process
  • Create/Replace GCP Service Accounts needed for the release process
  • Create IAM bindings needed for the release process

/sig k8s-infra
/area infra/gcp
/priority important-soon
/milestone v1.30

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.

@k8s-ci-robot k8s-ci-robot added sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jan 22, 2024
@k8s-ci-robot
Copy link
Contributor

@ameukam: The label(s) area/infra/gcp cannot be applied, because the repository doesn't have them.

In response to this:

The official releases and patch releases are currently done use a Google project where GCB builds are triggered. We should migrate to a community-owned project (preferably k8s-release).

  • Migrate/rotate credentials needed for the release process
  • Create/Replace GCP Service Accounts needed for the release process
  • Create IAM bindings needed for the release process

/sig k8s-infra
/area infra/gcp
/priority important-soon
/milestone v1.30

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.

@ameukam
Copy link
Member Author

ameukam commented Jan 22, 2024

cc @kubernetes/release-engineering

@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 21, 2024
@xmudrii
Copy link
Member

xmudrii commented Apr 22, 2024

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 22, 2024
@ameukam
Copy link
Member Author

ameukam commented Jul 18, 2024

/priority backlog
/milestone clear
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence. labels Jul 18, 2024
@xmudrii
Copy link
Member

xmudrii commented Aug 27, 2024

I'll be looking into this
/assign

@BenTheElder
Copy link
Member

I think we successfully did one with this? cc @ameukam

@ameukam
Copy link
Member Author

ameukam commented Sep 12, 2024

Nope. Nothing started for this issue.

More docs:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. 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

No branches or pull requests

5 participants