tekton初次安装报错“containers with incomplete status: [place-tools]”

报错内容

在按照官方部署方式部署完毕以后，执行第一个taskrun的时候就报错了，报错如下

Status:
  Conditions:
    Last Transition Time:  2022-08-08T00:28:53Z
    Message:               pod status "Initialized":"False"; message: "containers with incomplete status: [place-tools]"
    Reason:                Pending
    Status:                Unknown
    Type:                  Succeeded
  Pod Name:                hello-pod-d8svh
  Start Time:              2022-08-08T00:28:53Z
  Steps:
    Container:  step-hello
    Name:       hello
    Waiting:
      Reason:  PodInitializing
  Task Spec:
    Steps:
      Args:
        Hello World!
      Command:
        echo
      Image:  ubuntu
      Name:   hello
      Resources:
Events:
  Type    Reason   Age                From     Message
  ----    ------   ----               ----     -------
  Normal  Started  29m (x2 over 29m)  TaskRun
  Normal  Pending  29m                TaskRun  Pending
  Normal  Pending  29m                TaskRun  pod status "Initialized":"False"; message: "containers with incomplete status: [place-tools]"

研究了半天也没整明白咋回事，后来还是经过好兄弟提醒，发现在tekton-pipelines-controller这个Deployment的arg参数中指定了很多的镜像，全部都是外网的引用不到，所以报错了。
我这里把deployment的镜像下载下来传到了私有镜像仓库，却没看到args中的镜像

      containers:
        - name: tekton-pipelines-controller
          image: 172.17.68.213/tekton/tekton-controller:v0.27.3
          args: [
            # These images are built on-demand by `ko resolve` and are replaced
            # by image references by digest.
            "-kubeconfig-writer-image", "gcr.io/tekton-releases/github.com/tektoncd/pipeline/cmd/kubeconfigwriter:v0.27.3@sha256:ad7e35271347eb966e31e62f9301b7ee9072f14d25023fc6cfb46b7a7dba9c80", "-git-image", "gcr.io/tekton-releases/github.com/tektoncd/pipeline/cmd/git-init:v0.27.3@sha256:ff55dec12cfd227cc3fa381befe1b49c1a301c481d3a416109cb6bc54c8c7d12", "-entrypoint-image", "gcr.io/tekton-releases/github.com/tektoncd/pipeline/cmd/entrypoint:v0.27.3@sha256:c60dd03cda4506c36c40625ee5a963fefc4721d076f30efb191c7268bef8dd72", "-nop-image", "gcr.io/tekton-releases/github.com/tektoncd/pipeline/cmd/nop:v0.27.3@sha256:725760d6347f91deb6271998cf614a31dad54ba8dbe9fef5ac66256ac15973a2", "-imagedigest-exporter-image", "gcr.io/tekton-releases/github.com/tektoncd/pipeline/cmd/imagedigestexporter:v0.27.3@sha256:de7efad55330564841300537dfa43c45a5bdcbbb70685bb320bd7872dcbdc395", "-pr-image", "gcr.io/tekton-releases/github.com/tektoncd/pipeline/cmd/pullrequest-init:v0.27.3@sha256:d6c457a40e0648775d5651f3d80866c9eb43533a94a9f7d461f0e6dae507d0af",
            # This is gcr.io/google.com/cloudsdktool/cloud-sdk:302.0.0-slim
            "-gsutil-image", "gcr.io/google.com/cloudsdktool/cloud-sdk@sha256:27b2c22bf259d9bc1a291e99c63791ba0c27a04d2db0a43241ba0f1f20f4067f",
            # The shell image must be root in order to create directories and copy files to PVCs.
            # gcr.io/distroless/base:debug as of Apirl 17, 2021
            # image shall not contains tag, so it will be supported on a runtime like cri-o
            "-shell-image", "gcr.io/distroless/base@sha256:aa4fd987555ea10e1a4ec8765da8158b5ffdfef1e72da512c7ede509bc9966c4"]
          volumeMounts:
            - name: config-logging
              mountPath: /etc/config-logging
            - name: config-registry-cert
              mountPath: /etc/config-registry-cert