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 tooling off of gs://kubernetes-jenkins #33381

Open
5 of 9 tasks
michelle192837 opened this issue Aug 28, 2024 · 2 comments
Open
5 of 9 tasks

Migrate tooling off of gs://kubernetes-jenkins #33381

michelle192837 opened this issue Aug 28, 2024 · 2 comments
Assignees
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. sig/testing Categorizes an issue or PR as relevant to SIG Testing.

Comments

@michelle192837
Copy link
Contributor

michelle192837 commented Aug 28, 2024

Follow-up to the control plane migration (#33350).

Tools like Kettle, TestGrid, and others read from gs://kubernetes-jenkins, but should switch to using the new bucket (gs://kubernetes-ci-logs) or something else if needed.

  • Ensure results from kubernetes-jenkins are synced to kubernetes-ci-logs (believe this is already done as part of the control plane migration?)
  • Migrate Kettle
  • Migrate TestGrid
  • Migrate other miscellaneous use
  • K8s Infra Prow writes to kubernetes-ci-logs instead of kubernetes-jenkins
  • Remove access permissions from kubernetes-jenkins
  • Update references to kubernetes-jenkins across repos
    • kubernetes-sigs / prow
    • (any others?)

/assign
/sig testing

@michelle192837 michelle192837 added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Aug 28, 2024
@k8s-ci-robot k8s-ci-robot added the sig/testing Categorizes an issue or PR as relevant to SIG Testing. label Aug 28, 2024
@jbpratt
Copy link
Contributor

jbpratt commented Sep 17, 2024

/assign

@michelle192837
Copy link
Contributor Author

michelle192837 commented Oct 11, 2024

Other updates (copying from Slack):

  • Purge messages on k8s-infra-kettle subscription
  • Stop the kettle deployment in kubernetes-public temporarily
  • Update k8s.io deployment.yaml
    • Auto-deploy should handle it once submitted?
    • Update deployment.yaml in test-infra as well, but nothing should care about that file

Kettle is updated, looks like it is now pulling from the new subscription successfully according to logs. (I'm not sure if it's correctly acking finished.json files since I don't know if we have an example of that yet 🤔 So still confirming that)

Okay good, it's acknowledging finished.json.
I think we're good to go on the Prow change then? I'm going to let the bucket sync run one more time then stop it temporarily, then we can submit the prow change and hopefully it all works smoothly?
Run has complete and the sync job is disabled!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Projects
None yet
Development

No branches or pull requests

3 participants