-
Notifications
You must be signed in to change notification settings - Fork 807
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.com gcp project kubernetes-jenkins #1310
Comments
At the moment it's not clear to me whether we can update prow.k8s.io to support different jobs writing to different buckets, or if we're going to have to make the change in lockstep. This is why migrating gs://kubernetes-jenkins needs a proposal |
/lifecycle frozen |
On the occasion of moving things out of the SIG scalability uses this bucket to store master and node logs separately from the
|
@tosi3k Do you want the contents of this bucket to be preserved? if yes, what is the estimated size of |
Ref: kubernetes#1310 (comment). Part of kubernetes#1469. Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
We just need the last 90 days of the contents therein. I wonder - would applying some retention policy to After we migrate the scalability job configs to use
I don't know but if we were to introduce a 90d retention policy mechanism we would probably comfortably fit in 5 TBs. This is the size of the bucket after 97 days of existence: |
/milestone v1.23 |
/milestone v1.24 |
/milestone clear |
I'm working on eliminating old unused buckets from this project. kubernetes-jenkins and sig-scalability-logs still need a plan. There's also the mysterious kubernetes-jenkins-gcslogs which has content written to it recently judging by the file names but we can't tell where from yet ... |
Circled back:
Cleaning that up now. |
|
Opened kubernetes/test-infra#33248 for getting rid of |
Thank you! The only remaining reference is k8s.io/apps/gcsweb/deployment.yaml Line 36 in a554228
Later we should drop write permissions to this bucket, and then when we still don't see issues then we should drop it from gcsweb (no rush ...) |
so mostly we need to migrate off of |
/remove-lifecycle frozen |
Part of umbrella issue to migrate away from google.com gcp projects: #1469
Umbrella issue for migrating or removing dependence on all of the kubernetes project infra that lives under kubernetes-jenkins:
GCS buckets:
gsutil ls -p kubernetes-jenkins | grep -v kubernetes-staging- | sed -e 's/.*/- [ ] `&`/'
gs://artifacts-upload-test/
: TODO: ???gs://artifacts.kubernetes-jenkins.appspot.com/
: TODO: sincerely doubt we need to migrate GCR bucketsgs://gcf-sources-661044217466-us-central1/
: TODO: going to assume we can ignore thisgs://k8s-bazel-cache/
: May be used by kubernetes/kubernetes bazel, may be defunct? Last updated files 2019-03-11gs://k8s-kops-gce/
: TODO: ???gs://kubernetes-e2e-soak-configs/
: TODO: ???gs://kubernetes-federation-release/
: TODO: ??? for this and the other federation buckets, surely these aren't usedgs://kubernetes-federation-release-1-4/
gs://kubernetes-federation-release-1-5/
gs://kubernetes-federation-release-1-6/
gs://kubernetes-federation-release-1-7/
gs://kubernetes-federation-release-1-8/
gs://kubernetes-federation-release-jenkins/
: TODO: ???gs://kubernetes-federation-release-serial/
: TODO: ???gs://kubernetes-jenkins/
: hosts all logs/artifacts from prow.k8s.io, will need a plan/proposalgs://kubernetes-jenkins-gcslogs/
: definitely do not migrategs://kubernetes-jenkins-old/
: TODO: : we probably don't care if this is migratedgs://kubernetes-release-dev-jenkins/
: TODO: this probably shouldn't be migratedgs://kubernetes-test-history/
: we can ignore thisgs://sig-scalability-logs/
: should happen as part of Migrate away from google.com gcp project kubernetes-scale #2241gs://us.artifacts.kubernetes-jenkins.appspot.com/
: TODO: sincerely doubt we need to migrate GCR bucketsService Accounts:
I'm not sure of everything I am (not) allowed to list here. So this isn't an exhaustive list. But we should make sure none of the service accounts in this project are used in any IAM bindings in kubernetes.io. Googlers will need to help identify this.
kubekins@kubernetes-jenkins.iam.gserviceaccount.com
- This is the big one, identify when/where this has access to services/resources that should be migrated or have equivalents stood up in kubernetes.iotest-owners@kubernetes-jenkins.iam.gserviceaccount.com
queue-health@kubernetes-jenkins.iam.gserviceaccount.com
The text was updated successfully, but these errors were encountered: