Use hub.docker.com to mirror the images that will be used by OpenPAI hosted on gcr.io.

[siaimes]

Use hub.docker.com to mirror the image that will be used by OpenPAI hosted on gcr.io.

Signed-off-by: siaimes 34199488+siaimes@users.noreply.github.com

[coveralls]

Coverage remained the same at 33.681% when pulling 85f8b61 on siaimes:mirror_gcr_io into ea19af1 on microsoft:master.

[siaimes]

Ref: https://github.com/AliyunContainerService/image-syncer

1. Add DOCKERHUB_USERNAME and DOCKERHUB_PASSWORD secrets with username and token of hub.docker.com:

2. Every time a new version is released, the workflow will synchronize the image of gcr.io to the designated registry:

3. For users who cannot access gcr.io, just add the following lines to the configuration file, and then run the installation script, everything will be fine:

openpai_kubespray_extra_var:
  kube_image_repo: "DOCKERHUB_USERNAME"
  gcr_image_repo: "DOCKERHUB_USERNAME"
  pod_infra_image_repo: "DOCKERHUB_USERNAME/pause-{{ image_arch }}"
  dnsautoscaler_image_repo: "DOCKERHUB_USERNAME/cluster-proportional-autoscaler-{{ image_arch }}"

example:

Because we only synchronize the images required by this project, I think there should be no abuse issues.