Updates k8s dependencies to 0.28 and controller-runtime to v0.15.
All the other PRs update k8s dependencies to 0.27 but this one updates to 0.28 because of the following error:
../../../../pkg/mod/k8s.io/kubectl@v0.25.0/pkg/describe/describe.go:2667:65: cannot use ing.Status.LoadBalancer (variable of type "k8s.io/api/networking/v1".IngressLoadBalancerStatus) as "k8s.io/api/core/v1".LoadBalancerStatus value in argument to loadBalancerStatusStringer
and kubectl 0.28 was the only comptabile version.
With the update to controller-runtime v0.15 (changes in release detailed here), this PR has following changes to combat the breaking changes:
NewClient creation does not fail, so tests where the client is expected to fail specific api call needs to be made
replace apimachinery/runtime client with controller-runtime/client
Changes wrt - https://issues.redhat.com/browse/SANDBOX-675
DO NOT MERGE (All the PRs related to version updates need to be merged at once, but these PR are for early feedback so that there are not a lot of changes to review at once)
Updates k8s dependencies to 0.28 and controller-runtime to v0.15.
All the other PRs update k8s dependencies to 0.27 but this one updates to 0.28 because of the following error:
../../../../pkg/mod/k8s.io/kubectl@v0.25.0/pkg/describe/describe.go:2667:65: cannot use ing.Status.LoadBalancer (variable of type "k8s.io/api/networking/v1".IngressLoadBalancerStatus) as "k8s.io/api/core/v1".LoadBalancerStatus value in argument to loadBalancerStatusStringer
and kubectl 0.28 was the only comptabile version.
With the update to controller-runtime v0.15 (changes in release detailed here), this PR has following changes to combat the breaking changes:
Changes wrt - https://issues.redhat.com/browse/SANDBOX-675 DO NOT MERGE (All the PRs related to version updates need to be merged at once, but these PR are for early feedback so that there are not a lot of changes to review at once)