Benjamin Elder

```console $ gsutil cat gs://kubernetes-ci-logs/logs/ci-kubernetes-e2e-gci-gce/latest-build.txt 189489678293716582 ``` But the page starts at [1868710627107672064](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gci-gce/1868710627107672064) from december. Testgrid goes up to 1894896782937165824 as the currently running job.

Huh, when I refresh I'm getting different results at https://prow.k8s.io/job-history/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gci-gce Each subsequent load has had newer results. I'm up to mid january ...

It's not quite reliably loading newer runs on subsequent loads but they have averaged newer, They're reliably at least the current month now (still weeks old). Very strange ...

Thanks! The last few times we've had issues with prow.k8s.io we've eventually root-caused them to migrating the CI to SIG K8s Infra and configuration issues etc so I didn't want...

/remove-lifecycle stale still true: https://prow.k8s.io/job-history/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gci-gce (also it's pretty slow to load initially, which makes me think it's not reading the latest-build.txt https://storage.googleapis.com/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gci-gce/latest-build.txt manually using the latest build.txt value works, but...

/assign @kubernetes/contributor-comms

> Hello! as an effort to better triage the issues from the questions/discussions and troubleshooting, we added a [discussions](https://github.com/kubeflow/pipelines/discussions) tab in the repo. Please move your topic to the new...

note: you can directly replace the host with registry.k8s.io, we have carried forward all images to date. gcr.io/google-containers -> registry.k8s.io k8s.gcr.io -> registry.k8s.io

There is an existing discussion in https://github.com/kubernetes-sigs/kind/issues/3124 https://github.com/kubernetes-sigs/kind/issues/2376 https://github.com/kubernetes-sigs/kind/issues/2114. We haven't settled on the tagging scheme yet. However, you should use digests anyhow for other reasons including security (trust of...

> The sha256 digest also makes it more difficult to run kind in air-gapped environment. > I exported (docker save) the image from one host and copy to the air-gapped...