ISSUE: Pull quotas Dockerhub for Equinor organisation

[emirgens]

• Order team (Service account) for docker hub, to be able to build our Radix applications (handled in a separate task)
• add script to store docker.com username and access token in keyvault #1433
• create external secret for radix-registry-default-auth radix-flux#2346
• Add support for default dockerhub credentials when pulling images for components and jobs radix-operator#1181
  • release - release radix-operator radix-operator#1184
• radix-flux: set externalRegistryDefaultAuthSecret for radix-operator:
  • development - set externalRegistryDefaultAuthSecret for radix-operator in development radix-flux#2359
  • playground - set externalRegistryDefaultAuthSecret for radix-operator in playground radix-flux#2365
  • platform - set externalRegistryDefaultAuthSecret for radix-operator in platform radix-flux#2366
  • c2 - set externalRegistryDefaultAuthSecret for radix-operator in c2 radix-flux#2367
• Add support for default dockerhub credentials in radix-pipeline-runner  radix-operator#1174
  • release - Use radix external registry default auth secret in buildah (#1187) radix-operator#1190
• add fedcred for repo radix-buildkit-builder to MIs radix-id-acr-workflows #1445
• set buildkitImageBuilder for playground, platform and c2 radix-flux#2374
• add radix-buildkit-builder to radix-acr-cleanup whitelist radix-flux#2386
• Update radix-private
  • https://github.com/equinor/radix-private/pull/272
  • Should we add info here about the k8s secret radix-external-registry-default-auth? (handled in a separate task)
• Add to SNYK

Where should we document the use of default external registry credentials (for docker.io)? radix-private?

For now it is OK to temporary use one of the team members account while waiting for a service account.