image-promo job is hitting quota limits about k8s.io

[chrischdi]

Opened the issue at promo-tools. Maybe I can find some time to take a look where it could get optimised. Thanks for pointing to the right direction @BenTheElder ! Really appreciating it 🚀

[BenTheElder]

This is not getting visibility to the right people, please file a bug with kubernetes-sigs/promo-tools or kubernetes/sig-release.

K8s-Infra is not changing the limits on the backing registries, they are roughly equivalent to the previous non-configurable GCR limits and they're necessary to prevent trivial DOS, even the project itself must not be permitted to self-DOS, and there is no way to exempt a single user.

[schrej]

/area registry.k8s.io
/area infra/gcp

[BenTheElder]

The image promoter makes a really high amount of API calls because of the approach to image signatures.

We have not changed the quotas in the infrastructure projects.

/transfer kubernetes-sigs/promo-tools
/sig release

[k8s-ci-robot]

@BenTheElder: Something went wrong or the destination repo kubernetes/kubernetes-sigs/promo-tools does not exist.

In response to this:

The image promoter makes a really high amount of API calls because of the approach to image signatures.

We have not changed the quotas in the infrastructure projects.

/transfer kubernetes-sigs/promo-tools
/sig release

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[BenTheElder]

The image promoter is at https://github.com/kubernetes-sigs/promo-tools

[chrischdi]

Happened today too for a CAPV release:

https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/post-k8sio-image-promo/1776261613632884736