Update api, client-go, apiserver-library-go to use CI config from repo

[damemi]

Needed for go1.17 bumps for 1.23 rebase
Following the same steps that were done in #24201 for library-go

.ci-operator.yaml is added in the following PRs:

• Add .ci-operator.yaml client-go#204
• Add .ci-operator.yaml apiserver-library-go#77
• Add .ci-operator.yaml api#1077

[damemi]

/cc @soltysh
ptal

[openshift-ci]

@damemi: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/rehearse/openshift/api/master/verify-deps	6553afb	link	unknown	/test pj-rehearse
ci/rehearse/openshift/api/master/unit	6553afb	link	unknown	/test pj-rehearse
ci/rehearse/openshift/api/master/build	6553afb	link	unknown	/test pj-rehearse
ci/rehearse/openshift/api/master/verify	6553afb	link	unknown	/test pj-rehearse
ci/rehearse/openshift/api/master/verify-client-go	6553afb	link	unknown	/test pj-rehearse
ci/rehearse/openshift/apiserver-library-go/master/unit	6553afb	link	unknown	/test pj-rehearse
ci/rehearse/openshift/apiserver-library-go/master/verify-deps	6553afb	link	unknown	/test pj-rehearse
ci/rehearse/openshift/apiserver-library-go/master/verify	6553afb	link	unknown	/test pj-rehearse
ci/rehearse/openshift/client-go/master/verify	6553afb	link	unknown	/test pj-rehearse
ci/prow/pj-rehearse	6553afb	link	false	/test pj-rehearse

Full PR test history. Your PR dashboard.

Details

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.

[soltysh]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: damemi, soltysh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• ci-operator/config/openshift/api/OWNERS [soltysh]
• ci-operator/config/openshift/apiserver-library-go/OWNERS [soltysh]
• ci-operator/config/openshift/client-go/OWNERS [soltysh]
• ci-operator/jobs/openshift/api/OWNERS [soltysh]
• ci-operator/jobs/openshift/apiserver-library-go/OWNERS [soltysh]
• ci-operator/jobs/openshift/client-go/OWNERS [soltysh]

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

[openshift-bot]

/retest-required

Please review the full test history for this PR and help us cut down flakes.

[openshift-ci]

@damemi: Updated the following 2 configmaps:

• ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-api-master.yaml using file ci-operator/config/openshift/api/openshift-api-master.yaml
  • key openshift-apiserver-library-go-master.yaml using file ci-operator/config/openshift/apiserver-library-go/openshift-apiserver-library-go-master.yaml
  • key openshift-client-go-master.yaml using file ci-operator/config/openshift/client-go/openshift-client-go-master.yaml
• job-config-master-presubmits configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-api-master-presubmits.yaml using file ci-operator/jobs/openshift/api/openshift-api-master-presubmits.yaml
  • key openshift-apiserver-library-go-master-presubmits.yaml using file ci-operator/jobs/openshift/apiserver-library-go/openshift-apiserver-library-go-master-presubmits.yaml
  • key openshift-client-go-master-presubmits.yaml using file ci-operator/jobs/openshift/client-go/openshift-client-go-master-presubmits.yaml

Details

In response to this:

Needed for go1.17 bumps for 1.23 rebase
Following the same steps that were done in #24201 for library-go

.ci-operator.yaml is added in the following PRs:

• Add .ci-operator.yaml client-go#204
• Add .ci-operator.yaml apiserver-library-go#77
• Add .ci-operator.yaml api#1077

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.