[release-4.14] OCPBUGS-19701: Remove dependency on k8s.io/kubernetes packages

[openshift-cherrypick-robot]

This is an automated cherry-pick of #3913

/assign djoshy

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-18906 has been cloned as Jira Issue OCPBUGS-19701. Will retitle bug to link to clone.
/retitle [release-4.14] OCPBUGS-19701: Remove dependency on k8s.io/kubernetes packages

Details

In response to this:

This is an automated cherry-pick of #3913

/assign djoshy

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.

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-19701, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.14.0) matches configured target version for branch (4.14.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-18906 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-18906 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
• bug has dependents

Requesting review from QA contact:
/cc @sergiordlr

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #3913

/assign djoshy

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.

[yuqi-zhang]

/lgtm
/label backport-risk-assessed

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, yuqi-zhang

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:

• OWNERS [yuqi-zhang]

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

[openshift-ci]

@openshift-cherrypick-robot: 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/prow/okd-scos-e2e-gcp-op	08711a6	link	false	/test okd-scos-e2e-gcp-op
ci/prow/e2e-gcp-ovn-rt-upgrade	08711a6	link	false	/test e2e-gcp-ovn-rt-upgrade
ci/prow/e2e-gcp-rt-op	08711a6	link	false	/test e2e-gcp-rt-op

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.

[sergiordlr]

Verified using IPI on GCP

All critical test cases passed

These test cases were executed and passed:

"[sig-mco] MCO Layering Author:sregidor-ConnectedOnly-Longduration-NonPreRelease-Medium-54056-Update osImage using the internal registry to store the image [Disruptive] [Serial]"
"[sig-mco] MCO Author:sregidor-NonPreRelease-Longduration-Medium-57595-Use empty pull-secret[Disruptive] [Serial]"
"[sig-mco] MCO Author:mhanss-NonPreRelease-Longduration-High-42680-change pull secret in the openshift-config namespace [Serial]"
We can add the qe-approved label

/label qe-approved
/label cherry-pick-approved

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-19701: All pull requests linked via external trackers have merged:

• openshift/machine-config-operator#3940

Jira Issue OCPBUGS-19701 has been moved to the MODIFIED state.

Details

In response to this:

This is an automated cherry-pick of #3913

/assign djoshy

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.