Update dependencies of Operator and Executor

[RafalSkolasinski]

We should make sure that dependencies of Operator and Executor as as much up to date as it is possible.
Once we get both up-to-date we should keep it such using dependabot to avoid a big update in the future.

This will be a parent issue linking to smaller ones listed into a checklist:

Operator Upgrade

• Assessment required
• Upgrade all dependencies that upgrade is straightforward (Upgrade Operator dependencies that can be bumped without problems #2098)
• Upgrace k8s.io deps to v0.17.8 at least (Upgrade Operator dependencies that can be bumped without problems #2098)
• Upgrade Zap to v1.15.0 (bump zap from v1.10.0 to v1.15.0 #2127)
• Upgrade istio.io deps (upgrade istio.io dependencies in operator #2126)
• Upgrade knative.dev deps (Upgrade knative.dev deps in Operator #2128)
• Verify issue with go-logr (Unable to get log kubernetes-sigs/controller-runtime#1033)
• Update controller-runtime (Upgrade controller-runtime in Operator #2116)

Executor Upgrade

• Assessment required
• Upgrade all dependencies that upgrade is straightforward (Upgrade Executor dependencies that can be bumped without problems #2089)
• Refactor logging to lift dependency on controller-runtime (Refactor logging in Executor #2090)
• Upgrade Zap to v1.15.0 (bump zap from v1.10.0 to v1.15.0 #2127)
• Upgrade Operator version in Executor deps (Upgrade Operator version in Executor deps #2091)
• Upgrade k8s.io deps (Upgrade k8s.io dependencies in the Executor #2134)
• Remove dependency on client-go (Remove Executor's dependency on client-go #2092)

Both

• Verify that all direct dependencies are upgraded to reasonably recent versions
• Verify possible issues with dependencies marked as incompatible

Dependabot Integration:

• Operator
• Executor

Update

• We are note removing Executor's dependency on Operator refactoring logging to lift dependency controller-runtime is not crucial for this task
• Instead of fixing Operator version in Executor update version of operator in executor deps #2121 will build Executor using Operator from monorepo (replace method in go.mod + symlinking operator folder)
• go-logr package is interface definition and incompatibility seems to be present in our dependencies. As this is only interface definition updating it is not a priority for this issue

Attachments

Executor upgrade assessment

[RafalSkolasinski]

Initial assessment for Operator

[RafalSkolasinski]

More info on go-logr and controller-runtime incompatibility issues:

• ⚠️ Update go-logr/logr v0.1.0 -> v0.2.0 kubernetes-sigs/controller-runtime#995
• ⚠️ Support go-logr/logr@v0.2.0 kubernetes-sigs/controller-runtime#1011
• Unable to get log kubernetes-sigs/controller-runtime#1033
• Add InfoLogger type alias for compatibility go-logr/logr#20

[RafalSkolasinski]

+incomaptible comment in go.mods means incompatibility in different ways that Go uses to handle dependencies.

good read: https://stackoverflow.com/a/57372286/5420500

[RafalSkolasinski]

With 2nd level dependencies (and further) we have very limited control as this is basically set by 1st level dependencies.
We will need to raise issues directly in upstream projects in case there is an CVE or another important reason to upgrade arise.