OPNET-415: Upgrade o/api to include extended network config

[mkowalski]

Infra CR allows now to more extensive configuration of host networking (implemented as openshift/api#1695).

This PR gets those changes into the installer.

We are forcefully making k8s.io/api and k8s.io/apimachinery to stay at v0.28.3 because their bump to v0.29.0 should happen as a separate task.

[openshift-ci-robot]

@mkowalski: This pull request references OPNET-415 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 story to target the "4.16.0" version, but no target version was set.

Details

In response to this:

Infra CR allows now to more extensive configuration of host networking (implemented as openshift/api#1695).

This PR gets those changes into the installer.

We are forcefully making k8s.io/api and k8s.io/apimachinery to stay at v0.28.3 because their bump to v0.29.0 should happen as a separate task.

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.

[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

[mkowalski]

/test all

[mkowalski]

/cc @JoelSpeed
/cc @cybertron

As reviewers of the o/api change

/cc @zaneb

As approver of installer

[sadasu]

@mkowalski are additional changes required within the Installer while generating the Infra manifest for the platforms that are updated with the opnshift/api changes?

[mkowalski]

are additional changes required within the Installer while generating the Infra manifest for the platforms that are updated with the opnshift/api changes?

@sadasu, once this PR with API update merges I will ask for review of #7604 which is responsible for filling the new fields.

The reason I don't do it in a single PR is that it is not mandatory to have those new fields with values immediately, thus merging the API update without code updating new values is not going to break anything

[sadasu]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bbethell-1, sadasu

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 [sadasu]

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

[cybertron]

/lgtm

[openshift-ci]

@mkowalski: all tests passed!

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.