ref: @spiffxp at kubernetes/kubernetes#97002 (comment):
https://kubernetes.slack.com/archives/C09QZ4DQB/p1606896985218000
The project hosting the GCR repo was swept up by a security audit because it hadn't been properly accounted for. That change has been reverted. Now waiting to see affected jobs go back to green.
We should create a community-owned equivalent project, I'll open a followup issue for that
gcr.io/k8s-authenticated-test
is the specific case here, but we should try to cover as many as we find.
/assign
/sig release
/area release-eng artifacts
cc: @kubernetes/release-engineering @kubernetes/ci-signal @thockin
Tagging since they also expressed interest:
@thejoycekung @jeremyrickard @aojea
EDIT(@spiffxp): Broke down into issues per GCP project
And not a GCP project, but
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4