quay.io/openshift-pipeline/tektoncd-pipeline-gsutil:v0.10.1 is not exist about pipelines-tutorial

[ckadner]

@kevinyu98 please add some detail to this issue

[ckadner]

Normal    Pulling   10m (x7 over 21m)     kubelet, 10.221.112.173  Pulling image "quay.io/openshift-pipeline/tektoncd-pipeline-gsutil:v0.10.1"
Normal    BackOff   5m34s (x68 over 21m)  kubelet, 10.221.112.173  Back-off pulling image "quay.io/openshift-pipeline/tektoncd-pipeline-gsutil:v0.10.1"
Warning   Failed    36s (x90 over 21m)    kubelet, 10.221.112.173  Error: ImagePullBackOff

The image quay.io/openshift-pipeline/tektoncd-pipeline-gsutil:v0.10.1 does not exist:
https://quay.io/repository/openshift-pipeline/tektoncd-pipeline-gsutil?tab=tags

Originally posted by @Tomcli in kubeflow/kfp-tekton#38 (comment)

[ckadner]

@kevinyu98 -- did you use the openshift/tektoncd-pipeline-operator?

deploy/resources/v0.10.1/pipelines/release.yaml#L816 refers to image: quay.io/openshift-pipeline/tektoncd-pipeline-controller:v0.10.1:

    spec:
      serviceAccountName: tekton-pipelines-controller
      containers:
      - name: tekton-pipelines-controller
        image: quay.io/openshift-pipeline/tektoncd-pipeline-controller:v0.10.1
        args: [
          "-kubeconfig-writer-image", "quay.io/openshift-pipeline/tektoncd-pipeline-kubeconfigwriter:v0.10.1",
          "-creds-image", "quay.io/openshift-pipeline/tektoncd-pipeline-creds-init:v0.10.1",
          "-git-image", "quay.io/openshift-pipeline/tektoncd-pipeline-git-init:v0.10.1",
          "-nop-image", "quay.io/openshift-pipeline/tektoncd-pipeline-nop:v0.10.1",
          "-shell-image", "registry.access.redhat.com/ubi8/ubi-minimal:latest",
          "-gsutil-image", "quay.io/openshift-pipeline/tektoncd-pipeline-gsutil:v0.10.1",
          "-entrypoint-image", "quay.io/openshift-pipeline/tektoncd-pipeline-entrypoint:v0.10.1",
          "-imagedigest-exporter-image", "quay.io/openshift-pipeline/tektoncd-pipeline-imagedigestexporter:v0.10.1",
          "-pr-image", "quay.io/openshift-pipeline/tektoncd-pipeline-pullrequest-init:v0.10.1",
          "-build-gcs-fetcher-image", "quay.io/openshift-pipeline/tektoncd-pipeline-gcs-fetcher:v0.10.1",
        ]
        volumeMounts:
        - name: config-logging
          mountPath: /etc/config-logging
        env:

[ckadner]

See tektoncd-pipeline-operator/issues/239:

@chmouel removed the image in commit tektoncd/pipeline@f1692b9

Since upstream (ie pipeline) is not generating a binary wrapper anymore but using the google/cloud-sdk image directly..

I think in the mean time until we get this fixed you can update your deployment referencing this image directly...

@nikhil-thomas I have created openshift/tektoncd-pipeline#328 which would be used for next release, we can backport this to the release.yaml if you think so ? or wait for next release?

[ckadner]

@chmouel @nikhil-thomas -- how should we proceed here. Update some docs, add workarounds, change the operator, ...?

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.