kubernetes-sigs/promo-tools

image promoter should set a useragent

jonjohnsonjr opened this issue · 1 comments

What would you like to be added:

Ideally, the image promoter would have a unique useragent so we can identify what requests it's sending to the registry (in particular, to debug why you're getting 429s).

Why is this needed:

See #637 (comment)

/assign