OTA-1169: deps: bump openshift/api and k8s.io/client.go

[petr-muller]

Created with:

$ go get github.com/openshift/api
$ go get k8s.io/client-go@v0.29.0
$ go mod tidy
$ go mod vendor

I needed to bump the k8s.io/client.go as well because without that bump
I was getting:

go: github.com/openshift/cluster-version-operator/pkg/cvo imports
	k8s.io/client-go/kubernetes/scheme imports
	k8s.io/api/flowcontrol/v1alpha1: module k8s.io/api@latest found (v0.29.0), but does not contain package k8s.io/api/flowcontrol/v1alpha

[openshift-ci-robot]

@petr-muller: This pull request references OTA-1169 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set.

In response to this:

Created with:

$ go get github.com/openshift/api
$ go get k8s.io/client-go@v0.29.0
$ go mod tidy
$ go mod vendor

I needed to bump the k8s.io/client.go as well because without that bump
I was getting:

go: github.com/openshift/cluster-version-operator/pkg/cvo imports
  k8s.io/client-go/kubernetes/scheme imports
  k8s.io/api/flowcontrol/v1alpha1: module k8s.io/api@latest found (v0.29.0), but does not contain package k8s.io/api/flowcontrol/v1alpha

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[petr-muller]

   * could not run steps: step e2e-agnostic-operator failed: "e2e-agnostic-operator" post steps failed: failed to create or restart e2e-agnostic-operator-ipi-deprovision-deprovision pod: unable to create pod: Internal error occurred: resource quota evaluation timed out 

/retest
Looks like build05 had a hiccup, from https://prow.ci.openshift.org/?cluster=build05 it looks it may be temporary

[LalatenduMohanty]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: LalatenduMohanty, petr-muller

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 [LalatenduMohanty,petr-muller]

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

[wking]

openshift/release#47783 merged.

/test lint

[petr-muller]

/retest

[petr-muller]

/hold

This saw more failures than I feel comfortable with, I want to look at results before it merges even if the last retest is green

[openshift-ci]

@petr-muller: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[petr-muller]

Looking at https://prow.ci.openshift.org/pr-history/?org=openshift&repo=cluster-version-operator&pr=1022:

• azure issue 1 2
• build05 issue 1 2 3 4
• installation failure, does not seem CVO-related 1

So no actual test failure, just a single installation fail that seems unrelated to CVO. Looks good to me.

[petr-muller]

/hold cancel
/label no-qe

Labeling as no-qe because there is no new functionality. I do not consider this bump risky enough to do a dedicated regression run before merge (it is also early in the cycle).