Upgrade Kubernetes dependencies to 0.19.2

[rawlingsj]

We're using the Tekton client in a couple of places and are currently upgrading all our golang Kubernetes dependencies to 0.19.2. This includes an upgraded Kubernetes client-go which requires fixing up code due to breaking API changes.

I've just noticed there's a similar PR #3319 although that doesn't go all the way to 0.19.2 so I wonder if we should combine the two efforts or keep them separate?

Right now I have made these changes on a fork https://github.com/rawlingsj/pipeline/tree/k8s_0.19.2

I'm not sure I've done everything that's needed to upgrade:

• updated the go.mod file
• make vendor
• go mod vendor
• clientgofix ./... to fix breaking API changes from client-go https://github.com/kubernetes-sigs/clientgofix/
• make generated
• manually fixed up breaking API changes from generated clients
• make all

A couple of questions

1. Not sure if there are other steps that are needed above?
2. Did you want a PR for these changes and if so should I look to combine with Upgrade knative -> 0.18 #3319 or just keep them separate?

[jerop]

/kind question
/priority backlog (owners will review)
/area dependency

[afrittoli]

Does this require an update to the minimum version?
In case we need to document the min version required for Tekton.

[ghost]

It looks as though this will happen naturally when we upgrade to knative 0.21.

[dprotaso]

The above PR bumped the k8s deps

[dprotaso]

Right now knative.dev/pkg is tracking the main branch instead of the 0.20 release.

[afrittoli]

This is closed by #3724