cannot deploy pipeline with release.yaml

[qingchuwudi]

Expected Behavior

Actual Behavior

Deploy pipeline with kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.42.0/release.yaml.

While pipeline controller deploy failed, and the pod output with the log:

flag provided but not defined: -git-image
Usage of /ko-app/kubeconfigwriter:
-clusterConfig string
json string with the configuration of a cluster based on values from a cluster resource. Only required for external clusters.
-destinationDir string
destination directory where generated kubeconfig file will be stored. 

Steps to Reproduce the Problem

1. kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.42.0/release.yaml

Additional Info

• Tekton Pipeline version: v0.41.x ~ v0.42.0

More

I find it that the Entrypoint in the image .../controller:v0.40.2 is /ko-app/controller, but it has been changed to /ko-app/kubeconfigwriter in .../controller:v0.42.0 .

[qingchuwudi]

resolved

[Yongxuanzhang]

Hi I'm curious how does this issue happen and how it is resolved? @qingchuwudi thanks!

[tekton-robot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale with a justification. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten with a justification. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen with a justification. Mark the issue as fresh with /remove-lifecycle rotten with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen with a justification. Mark the issue as fresh with /remove-lifecycle rotten with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

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.