Bump tekton-pipeline to v0.17.1

[xiujuan95]

Fix issue: #429

• Bump to tekton-pipeline v0.17.1

Bump go modules to point to v0.17.1 tekton-pipeline version;

Modify vendor directory and make it have all new dependencies;

Add some dependent packages to fix some Incompatible issues:

• k8s.io/apimachinery => k8s.io/apimachinery v0.17.6

k8s.io/klog/v2
# k8s.io/klog/v2
vendor/k8s.io/klog/v2/klog.go:1241:34: cannot use logging.logr.V(int(level)) (type logr.InfoLogger) as type logr.Logger in field value:
        logr.InfoLogger does not implement logr.Logger (missing Error method)

v0.17.6 can solve above issue.

• sigs.k8s.io/controller-runtime => sigs.k8s.io/controller-runtime v0.5.2

k8s.io/klog/v2
# k8s.io/klog/v2
vendor/k8s.io/klog/v2/klog.go:1241:34: cannot use logging.logr.V(int(level)) (type logr.InfoLogger) as type logr.Logger in field value:
        logr.InfoLogger does not implement logr.Logger (missing Error method)
sigs.k8s.io/controller-runtime/pkg/webhook/internal/certwatcher

v0.5.2 can get rid of this issue.

• k8s.io/kube-openapi => k8s.io/kube-openapi v0.0.0-20200410145947-bcb3869e6f29

vendor/k8s.io/kube-openapi/pkg/util/proto/document.go:24:2: case-insensitive import collision: "github.com/googleapis/gnostic/openapiv2" and "github.com/googleapis/gnostic/OpenAPIv2"
make: *** [build/_output/bin/build-operator] Error 1

v0.0.0-20200410145947-bcb3869e6f29 can solve this issue.

• github.com/go-logr/logr => github.com/go-logr/logr v0.1.0

github.com/go-logr/zapr
# github.com/go-logr/zapr
vendor/github.com/go-logr/zapr/zapr.go:133:34: undefined: logr.InfoLogger

v0.2.0 release doesn't have logr.InfoLogger

[openshift-ci-robot]

Hi @xiujuan95. Thanks for your PR.

I'm waiting for a shipwright-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[qu1queee]

I will take a look today, I want this to get in asap.

[SaschaSchwarze0]

/ok-to-test

[SaschaSchwarze0]

Please update the README.md. The Tekton version is mentioned twice.

[adambkaplan]

/hold

There are multiple changes to k8s deps that impact operator-sdk. I am working on a separate PR to bump operator-sdk and k8s - it seems that Tekton needs to be bumped in that PR as well. See #443

[qu1queee]

@adambkaplan I took a look on this, Im not sure if this PR should be blocked. Please refer to this branch where I pinned the missing dependencies that this PR didnt.

Also, it seems Tekton is doing the same, look at their go modules in v0.17.1 vs master . Is there any specific reason on why this one should be blocked? if not I suggest that @xiujuan95 fixes the PR and then we put on top your upcoming #443

[zhangtbj]

Hi @adambkaplan ,

Any update in your PR?

Will you bump the Tekton in your PR or can we continue this PR?

[zhangtbj]

Hi @adambkaplan ,

This PR blocks our work recently. If your PR cannot finish soon.

I suggest we go ahead and accept this PR first. Please let us know if you have any comment or suggestion.

I plan to unblock this issue tomorrow if no other objection.

Thanks!

[zhangtbj]

/ok-to-test

[zhangtbj]

/ok-to-test

[zhangtbj]

/unhold

[zhangtbj]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: zhangtbj

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [zhangtbj]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment