[Registry] Can't pull images but could push.

Summary
Pull from container registry fails but Push succeeds.

Steps to reproduce

1. Install Gitlab with Gitlab Operator on OpenShift, use default Minio as backend.
2. Run a CI to push images, success.
3. Try to pull images from it, failed.

Or just run following command also fails.
podman pull -tls-verify=false registry.***/gitlab-qit/guide-kubernetes-microprofile-config/system:master

What is the current bug behavior?
Here's what happend when I run podman pull -tls-verify=false registry.***/gitlab-qit/guide-kubernetes-microprofile-config/system:master.

# podman pull registry.***/gitlab-qit/guide-kubernetes-microprofile-config/system:master
Trying to pull registry.xxx/gitlab-qit/guide-kubernetes-microprofile-config/system:master...
  Get "http://gitlab-minio:9000/registry/docker/registry/v2/blobs/sha256/0f/0f0c27bc62d6cc5562a1ce1ce666b093ff0fd9d9206ec4253d8c2b51bbf34ca6/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=gitlab%2F20210527%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20210527T065441Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=***": dial tcp: lookup gitlab-minio: no such host
Error: Error parsing image configuration: Get "http://gitlab-minio:9000/registry/docker/registry/v2/blobs/sha256/0f/0f0c27bc62d6cc5562a1ce1ce666b093ff0fd9d9206ec4253d8c2b51bbf34ca6/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=gitlab%2F20210527%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20210527T065441Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=***": dial tcp: lookup gitlab-minio: no such host

What is the expected correct behavior?
Could pull images from my registry

GitLab Environment Info
GitLab Enterprise Edition 13.10.3-ee
OpenShift Version 4.6.22
GitLab Operator Commit c9d23b26