bump k8s to v1.20.7

[dprotaso]

Fixes: #2111

[codecov]

Codecov Report

Merging #2145 (2a46e22) into main (0f304f6) will decrease coverage by 0.06%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##             main    #2145      +/-   ##
==========================================
- Coverage   65.89%   65.82%   -0.07%     
==========================================
  Files         221      221              
  Lines        9344     9362      +18     
==========================================
+ Hits         6157     6163       +6     
- Misses       2914     2923       +9     
- Partials      273      276       +3     

Impacted Files	Coverage Δ
injection/clients/dynamicclient/fake/fake.go	64.28% <50.00%> (-35.72%)	⬇️
test/gcs/mock/mock.go	91.39% <0.00%> (-1.08%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0f304f6...2a46e22. Read the comment docs.

[dprotaso]

/hold

I'm going to try to make a shim client that preserved pre 1.20 dynamic client behaviour

[dprotaso]

hmm... that won't work cause they make a copy of gvrToList map

[dprotaso]

This PR should make eventing green: knative/eventing#5477 downstream.

Other changes are trivial string replacements with the exception of the client & a plugin

[dprotaso]

/hold cancel

[dprotaso]

/assign @n3wscott @markusthoemmes

[markusthoemmes]

Doublechecked the downstream failures:

• Serving has the same "different error message" thing that this has, trivial to fix
• Networking has the same.
• Client has a compile error. Would it make sense to stage that change first?
• Camel has already been dropped, so we can ignore.
• kn-plugin-admin has the same compile error as client, so I guess fixing client will fix it as well.

So this is LGTM! Thanks for unblocking that breaking change!

[markusthoemmes]

FWIW, just looked at the client failure: k8s.io/cli-runtime has to be bumped to 0.20.7 in that repo too (it's not inherited from here) and then a few tests fail due to that dynamic client breaking change. Alerted the client team about that and now waiting for confirmation to either go ahead or to stage a fix first.

[markusthoemmes]

/lgtm
/approve

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dprotaso, markusthoemmes

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 [dprotaso,markusthoemmes]

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