Migrate away from gs://kops-ci

kubernetes / k8s.io

Code and configuration to manage Kubernetes project infrastructure, including various *.k8s.io sites

https://git.k8s.io/community/sig-k8s-infra

Apache License 2.0

740 stars 826 forks source link

Migrate away from gs://kops-ci #2625

Closed ameukam closed 3 months ago

ameukam commented 3 years ago

Part of umbrella issue to migrate the kubernetes project away from use of GCP project google-containers: #1469

[x] Create a new GCS bucket writable by k8s-infra-prow-build GKE cluster (kops-ci to k8s-infra-kops-ci-results)
[x] Give kOps maintainers admin access to this bucket
[x] Add a canary jobs (duplicate of the ones writing to gs://kops-ci) that pushes to the new bucket
- ensure it's building and pushing appropriately
[ ] update jobs that pull from the new bucket
[x] get rid of the jobs that runs on the "default" cluster

/sig cluster-lifecycle /area jobs /help wanted

/assign @justinsb @johngmyers For Kops

/assign @spiffxp For wg-k8s-infra

k8s-ci-robot commented 3 years ago

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

In response to [this](https://github.com/kubernetes/k8s.io/issues/2625): >Part of umbrella issue to migrate the kubernetes project away from use of GCP project google-containers: #1469 > >- [ ] Create a new GCS bucket writable by k8s-infra-prow-build GKE cluster (`kops-ci` to `k8s-infra-kops-ci-results`) >- [ ] Give kOps maintainers admin access to this bucket >- [ ] Add a canary jobs (duplicate of the ones writing to gs://kops-ci) that pushes to the new bucket > - ensure it's building and pushing appropriately >- [ ] update jobs that pull from the new bucket >- [ ] get rid of the jobs that runs on the "default" cluster > >/sig cluster-lifecycle >/area jobs >/help wanted > >/assign @justinsb @johngmyers >For Kops > >/assign @spiffxp >For wg-k8s-infra 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.

spiffxp commented 3 years ago

/priority important-longterm

spiffxp commented 3 years ago

/unassign I'm not actively working this, though I am happily reviewing @ameukam's PRs

spiffxp commented 3 years ago

/milestone clear Clearing from milestone because migrating all of the kops jobs over is likely to affect our spend in a not-insignificant way

k8s-triage-robot commented 2 years ago

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 commented 2 years ago

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

ameukam commented 2 years ago

/remove-lifecycle rotten /lifecycle frozen

ameukam commented 7 months ago

/milestone v1.31

upodroid commented 4 months ago

This migration is complete.

Are we missing something @ameukam ?

ameukam commented 4 months ago

I see references of the bucket: https://cs.k8s.io/?q=https%3A%2F%2Fstorage.googleapis.com%2Fkops-ci&i=nope&files=&excludeFiles=&repos=. 🤔

justinsb commented 4 months ago

I think we're really close, we were able to set up the 1.30 jobs with no kops-ci at all. I think there are still a few 1.28 / 1.29 jobs that point to kops-ci, but we can now repoint them following the example of 1.30 (we were waiting on releases on 1.28 / 1.29, I think they're now ~done)

ameukam commented 3 months ago

/close

What remaining is part of some legacy stuff and will probably go away.

k8s-ci-robot commented 3 months ago

@ameukam: Closing this issue.

In response to [this](https://github.com/kubernetes/k8s.io/issues/2625#issuecomment-2307416907): >/close > >What remaining is part of some legacy stuff and will probably go away. 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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.