Kettle subscribes to gs://kubernetes-ci-logs changes.

[michelle192837]

Switch kettle from the old PubSub subscription on kubernetes-jenkins to one on kubernetes-ci-logs.

Ref: #33381

(I believe no jobs care about this file, so this is just for consistency. The only auto-deploy job I found for Kettle is on the file in k8s.io:

test-infra/config/jobs/kubernetes/sig-k8s-infra/trusted/sig-k8s-infra-apps.yaml

Line 128 in cd57fdb

- name: post-k8sio-deploy-app-kettle

)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: michelle192837

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• kettle/OWNERS [michelle192837]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ameukam]

/lgtm

[BenTheElder]

note: I don't think we have an autodeploy for kettle.

https://kubernetes.slack.com/archives/CCK68P2Q2/p1729665831000469

[BenTheElder]

running: make -C kettle deploy

[BenTheElder]

... which doesn't work because the image doesn't exist, workaround: make -C kettle deploy TAG=latest

[michelle192837]

I don't think it has autodeploy, but I did redeploy kettle after this change (and verified it picked up changes from the PubSub subscription for a while after redeploy). Metrics on the subscription in kubernetes-public (https://pantheon.corp.google.com/cloudpubsub/subscription/detail/k8s-infra-kettle?e=13803378&mods=monitoring_api_prod&project=kubernetes-public&pageState=(%22duration%22:(%22groupValue%22:%22%22,%22customValue%22:%5B%222024-10-01T17:22:10.462Z%22,%222024-10-23T17:22:10.462Z%22%5D))) should confirm that.

[BenTheElder]

ah, thanks. it is not working however, I see a lot of errors in the logs about the build path being invalid in known bucket paths, meanwhile https://prow.k8s.io/job-history/gs/kubernetes-ci-logs/logs/metrics-kettle is failing due to the table being too old.

I think we need some more follow-up here.

[michelle192837]

Agreed, yeah. I tried to take a look into it (https://kubernetes.slack.com/archives/C7J9RP96G/p1729200222410669), but I didn't find anything obvious from my attempts :(

Fwiw the invalid build path errors do seem to exist in logs before metrics-kettle started having issues. Might still be an issues with the bucket switch...

Oh wait yeah. The deployment is using gcr.io/k8s-staging-infra-tools/kettle, but the latest image there is the Apr. 24 image. Auto-pushed images are pushed to gcr.io/k8s-staging-test-infra/kettle.

Edit: I'll make a fix for it.

[BenTheElder]

aha! thanks!

[BenTheElder]

Yeah I was puzzling over the code versus the logs and nothing made sense, so I started reading through #33490

makes sense that we're just using stale images

[dims]

thanks @michelle192837

[michelle192837]

(Oh also I think we do have auto-deploy for k8s.io deployment.yaml changes, I forgot.

test-infra/config/jobs/kubernetes/sig-k8s-infra/trusted/sig-k8s-infra-apps.yaml

Line 128 in 5749033

- name: post-k8sio-deploy-app-kettle

, https://testgrid.k8s.io/sig-k8s-infra-apps#deploy-kettle)

[dims]

good to know :) one less thing to worry about