Necessary changes that were brought in by API changes in Kubernetes c…

[jstourac]

…lient

Relevant XTF changes [1]. Kubernetes Client migration guide [2].

[1] xtf-cz/xtf#532
[2] https://github.com/fabric8io/kubernetes-client/blob/v6.0.0/doc/MIGRATION-v6.md

Description

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change
• Chore (non-breaking change which doesn't affect codebase;
  test, version modification, documentation, etc.)

Checklist

• Code contributed by me aligns with current project license: Apache 2.0
• Pull Request contains a description of the changes
• Pull Request does not include fixes for multiple issues/topics
• Code is self-descriptive and/or documented
• I have implemented unit tests to cover my changes
• I tested my code in OpenShift

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[jstourac]

/test all

[openshift-ci]

@jstourac: The following test 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/intersmash-e2e	f094e14	link	true	/test intersmash-e2e

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.

[jstourac]

I'm gonna close this - looks like there is already a followup MR #69.