feat(dependencies): Update k8s dependencies to 19.3. Fixes #4425

[NikeNano]

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
• The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
• My organization is added to USERS.md.
• I've signed the CLA.
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My builds are green. Try syncing with master if they are not.

[alexec]

This seems like something we want to target for v3. As a result we’d also need to update Argo events.

[NikeNano]

This seems like something we want to target for v3. As a result we’d also need to update Argo events.

ok, will take a look at evens when I succeed with workflows :). When is the target for v3 @alexec ?

[animeshsingh]

@NikeNano @alexec when is v3 targeted? We also have a blocker dependency on moving to k8s client higher version asap.

cc @Tomcli

[NikeNano]

@NikeNano when is v3 targeted? We also have a blocker dependency on moving to k8s client higher version asap.

Dont know, I try to look at this from time to time, but a lot of small things that needs to be updated @animeshsingh

[alexec]

v3 is target end of January. We should get this PR into that release.

[alexec]

See #4810