kubernetes / release

Release infrastructure for Kubernetes and related components
Apache License 2.0
484 stars 499 forks source link

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

Open ameukam opened 7 months ago

ameukam commented 7 months ago

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

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

k8s-ci-robot commented 7 months ago

@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](https://github.com/kubernetes/release/issues/3425): > >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](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.
k8s-ci-robot commented 7 months ago

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

In response to [this](https://github.com/kubernetes/release/issues/3425): > >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](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.
ameukam commented 7 months ago

cc @kubernetes/release-engineering

k8s-triage-robot commented 4 months ago

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

This bot triages un-triaged issues according to the following rules:

You can:

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

/lifecycle stale

xmudrii commented 4 months ago

/remove-lifecycle stale

ameukam commented 1 month ago

/priority backlog /milestone clear /lifecycle frozen

xmudrii commented 2 weeks ago

I'll be looking into this /assign

BenTheElder commented 3 days ago

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

ameukam commented 3 days ago

Nope. Nothing started for this issue.

More docs: