SPLAT-2582: Updated IPAM references to use v1beta2

[vr4manta]

SPLAT-2582

Changes

• Updated IPAM usage to use v1beta2 instead of v1beta1.

Notes

This is not a must have, but after recent bumps, we are getting a lot of warning messages about using the deprecated v1beta1 APIs.

After this change happens, installer will also need to be updated to generate IPAM v1beta2 versions of IPAddress and IPAddressClaims for vSphere static IP.

Currently vSphere static IP periodicals for 4.21+ are failing due to crd changes. Once those are fixed, this PR should have the static IP jobs pass with no warning messages for IPAddressClaims.

[openshift-ci-robot]

@vr4manta: This pull request references SPLAT-2582 which is a valid jira issue.

Details

In response to this:

SPLAT-2582

Changes

• Updated IPAM usage to use v1beta2 instead of v1beta1.

Notes

This is not a must have, but after recent bumps, we are getting a lot of warning messages about using the deprecated v1beta1 APIs.

After this change happens, installer will also need to be updated to generate IPAM v1beta2 versions of IPAddress and IPAddressClaims for vSphere static IP.

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-robot]

@vr4manta: This pull request references SPLAT-2582 which is a valid jira issue.

Details

In response to this:

SPLAT-2582

Changes

• Updated IPAM usage to use v1beta2 instead of v1beta1.

Notes

This is not a must have, but after recent bumps, we are getting a lot of warning messages about using the deprecated v1beta1 APIs.

After this change happens, installer will also need to be updated to generate IPAM v1beta2 versions of IPAddress and IPAddressClaims for vSphere static IP.

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign mdbooth for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[vr4manta]

/payload-job periodic-ci-openshift-release-master-nightly-4.21-e2e-vsphere-static-ovn

[openshift-ci]

@vr4manta: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.21-e2e-vsphere-static-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/91dca1f0-d460-11f0-9d86-f7e380d1078d-0

[openshift-ci-robot]

@vr4manta: This pull request references SPLAT-2582 which is a valid jira issue.

Details

In response to this:

SPLAT-2582

Changes

• Updated IPAM usage to use v1beta2 instead of v1beta1.

Notes

This is not a must have, but after recent bumps, we are getting a lot of warning messages about using the deprecated v1beta1 APIs.

After this change happens, installer will also need to be updated to generate IPAM v1beta2 versions of IPAddress and IPAddressClaims for vSphere static IP.

Currently vSphere static IP periodicals for 4.21+ are failing due to crd changes. Once those are fixed, this PR should have the static IP jobs pass with no warning messages for IPAddressClaims.

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.

[vr4manta]

Not sure why the TestReconcile/machine_with_node_likely_to_go_unhealthy test failed. I"ll retry later.

[damdo]

/test unit

[damdo]

/hold

We are working on a different fix, will keep you posted

[damdo]

cc. @mdbooth

[vr4manta]

/retest

[vr4manta]

/retest

[vr4manta]

Taking a deeper look at unit test issues

[vr4manta]

@damdo now that things have settled down, do we want to look into using this PR?

[vr4manta]

/retest

[openshift-ci]

@vr4manta: 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-sigs/prow repository. I understand the commands that are listed here.

[damdo]

@vr4manta yes we may wanna still do this

[perdasilva]

@vr4manta this has been open for a little while, is it still relevant?

[openshift-ci]

PR needs rebase.

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-sigs/prow repository.