[BUG]kubeblocks-dataprotection image cannot pull for insufficient_scope: authorization failed

[ahjing99]

kbcli version
Kubernetes: v1.27.3-gke.100
KubeBlocks: 0.7.0-alpha.3
kbcli: 0.7.0-alpha.3

     `kbcli kubeblocks install --create-namespace  --namespace default `

Kubernetes version 1.27.3
Kubernetes provider GKE
kbcli version 0.7.0-alpha.3
Collecting data from cluster                       OK
Kubernetes cluster preflight                       OK

Add and update repo kubeblocks                     OK
Install KubeBlocks 0.7.0-alpha.3                   FAIL
error: install chart kubeblocks error: release kubeblocks failed, and has been uninstalled due to atomic being set: timed out waiting for the condition
check kubeblocks status...
check kubeblocks resources status


k describe pod kubeblocks-dataprotection-6b9749986c-h2b6n
Name:         kubeblocks-dataprotection-6b9749986c-h2b6n
Namespace:    default
Priority:     0
Node:         gke-yjtest-default-pool-f59be211-2vqs/10.128.0.46
Start Time:   Thu, 31 Aug 2023 18:55:40 +0800
Labels:       app.kubernetes.io/instance=kubeblocks
              app.kubernetes.io/name=kubeblocks
              pod-template-hash=6b9749986c
Annotations:  <none>
Status:       Pending
IP:           10.104.1.106
IPs:
  IP:           10.104.1.106
Controlled By:  ReplicaSet/kubeblocks-dataprotection-6b9749986c
Init Containers:
  tools:
    Container ID:  containerd://27dc91f1b70e572cf895d87a3793bac7bbeb69e73bba4d0a957847acc0c0f44c
    Image:         registry.cn-hangzhou.aliyuncs.com/apecloud/kubeblocks-tools:0.7.0-alpha.3
    Image ID:      registry.cn-hangzhou.aliyuncs.com/apecloud/kubeblocks-tools@sha256:83bf9f1710d1b90d0fd4cd3d72f3bc67f46a0e40a983bca292abf5659efa20d2
    Port:          <none>
    Host Port:     <none>
    Command:
      /bin/true
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Thu, 31 Aug 2023 18:56:04 +0800
      Finished:     Thu, 31 Aug 2023 18:56:04 +0800
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-rbvcq (ro)
Containers:
  dataprotection:
    Container ID:
    Image:         registry.cn-hangzhou.aliyuncs.com/apecloud/kubeblocks-dataprotection:0.7.0-alpha.3
    Image ID:
    Ports:         9443/TCP, 8081/TCP, 8080/TCP
    Host Ports:    0/TCP, 0/TCP, 0/TCP
    Args:
      --health-probe-bind-address=:8081
      --metrics-bind-address=:8080
      --leader-elect
      --leader-elect-id=abd03fda
      --zap-devel=false
      --zap-time-encoding=iso8601
      --zap-encoder=console
    State:          Waiting
      Reason:       ImagePullBackOff
    Ready:          False
    Restart Count:  0
    Liveness:       http-get http://:health/healthz delay=15s timeout=1s period=20s #success=1 #failure=3
    Readiness:      http-get http://:health/readyz delay=5s timeout=1s period=10s #success=1 #failure=3
    Environment:
      CM_NAMESPACE:                    default
      CM_AFFINITY:                     {"nodeAffinity":{"preferredDuringSchedulingIgnoredDuringExecution":[{"preference":{"matchExpressions":[{"key":"kb-controller","operator":"In","values":["true"]}]},"weight":100}]}}
      CM_TOLERATIONS:                  [{"effect":"NoSchedule","key":"kb-controller","operator":"Equal","value":"true"}]
      KUBEBLOCKS_IMAGE_PULL_POLICY:    IfNotPresent
      KUBEBLOCKS_TOOLS_IMAGE:          registry.cn-hangzhou.aliyuncs.com/apecloud/kubeblocks-tools:0.7.0-alpha.3
      KUBEBLOCKS_SERVICEACCOUNT_NAME:  kubeblocks
      VOLUMESNAPSHOT:                  true
      VOLUMESNAPSHOT_API_BETA:         true
    Mounts:
      /etc/kubeblocks from manager-config (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-rbvcq (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  manager-config:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      kubeblocks-manager-config
    Optional:  false
  kube-api-access-rbvcq:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 kb-controller=true:NoSchedule
                             node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                    From               Message
  ----     ------     ----                   ----               -------
  Normal   Scheduled  5m10s                  default-scheduler  Successfully assigned default/kubeblocks-dataprotection-6b9749986c-h2b6n to gke-yjtest-default-pool-f59be211-2vqs
  Normal   Pulling    5m9s                   kubelet            Pulling image "registry.cn-hangzhou.aliyuncs.com/apecloud/kubeblocks-tools:0.7.0-alpha.3"
  Normal   Pulled     4m46s                  kubelet            Successfully pulled image "registry.cn-hangzhou.aliyuncs.com/apecloud/kubeblocks-tools:0.7.0-alpha.3" in 22.991430698s (22.991520661s including waiting)
  Normal   Created    4m46s                  kubelet            Created container tools
  Normal   Started    4m46s                  kubelet            Started container tools
  Normal   Pulling    3m15s (x4 over 4m43s)  kubelet            Pulling image "registry.cn-hangzhou.aliyuncs.com/apecloud/kubeblocks-dataprotection:0.7.0-alpha.3"
  Warning  Failed     3m13s (x4 over 4m41s)  kubelet            Failed to pull image "registry.cn-hangzhou.aliyuncs.com/apecloud/kubeblocks-dataprotection:0.7.0-alpha.3": rpc error: code = Unknown desc = failed to pull and unpack image "registry.cn-hangzhou.aliyuncs.com/apecloud/kubeblocks-dataprotection:0.7.0-alpha.3": failed to resolve reference "registry.cn-hangzhou.aliyuncs.com/apecloud/kubeblocks-dataprotection:0.7.0-alpha.3": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
  Warning  Failed     3m13s (x4 over 4m41s)  kubelet            Error: ErrImagePull
  Warning  Failed     2m59s (x4 over 4m11s)  kubelet            Error: ImagePullBackOff
  Normal   BackOff    3s (x16 over 4m11s)    kubelet            Back-off pulling image "registry.cn-hangzhou.aliyuncs.com/apecloud/kubeblocks-dataprotection:0.7.0-alpha.3"