establish a paid dockerhub account for the pull-through cache

Following #120 (closed).

This will allow us to go around the rate limits.

added A-registry p1 labels

changed iteration to Kubernetes Sprints Mar 5, 2025 - Mar 18, 2025

assigned to @rbritoda

Ticket with security team: RQF3079994

Ticket with the CLO: RQF3080495

added p2 label and removed p1 label

As a mitigation until we get this done we've increased the quota of the docker.io cache to 4TB.

Both tickets above agreed with going ahead with setting up a paid dockerhub account.

In contact with Valentina for the supplierdb and credit card logistics.

changed iteration to Kubernetes Sprints Mar 19, 2025 - Apr 1, 2025

DAI: https://edh.cern.ch/Document/SupplyChain/DAI/10937001

user/pass for the account being used in vault:

kv get kv/kubernetes/services/kops-registry/gpn/cache/docker.io

Service change: https://cern.service-now.com/service-portal?id=outage&n=OTG0155213

Dashboard to monitor pull activity from this account: https://hub.docker.com/orgs/cerncache/usage/pulls

@strigazi we can also consider using this account for the "out of cern" bootstrap registry?

yeap, we can push to cerncache.