OCPBUGS-43412: bump update k8s.io/* dependencies to v1.31.1 & openshift/api

[EmilienM]

• Update go.mod with k8s.io/* dependencies to v1.31.1 & openshift/api to a recent commit in order to bring the new floatingIP field for platform OpenStack
• make update test verify
• controller: adjustments for new control-runtime & ratelimit

Note: these commits have to be squashed together, in order to pass CI.

[openshift-ci-robot]

@EmilienM: This pull request explicitly references no jira issue.

In response to this:

• vendoring: update k8s.io/ dependencies to v1.31.1 & openshift/api*
• make update
• controller: adjustments for new control-runtime & ratelimit

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 candita for approval. For more information see the Kubernetes Code Review Process.

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

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

[EmilienM]

/test e2e-azure-ovn

[Miciah]

Thanks! Would you mind doing the following?

• Squash the commits so that make test verify will succeed for every commit in the history.
• Add a reference to https://issues.redhat.com/browse/OCPBUGS-43412 in the commit message, and add OCPBUGS-43412: to the PR title.
• Document the commands that you used in order to do the bump in the commit message.

For an example commit message from another k8s.io/* and controller-runtime vendor bump, see openshift/cluster-dns-operator@dee78ad.

[Miciah]

I'm guessing that the openshift/api and k8s.io/* bumps cannot be done in separate PRs. Could you mention that in the commit message, and mention that the openshift/api bump brings in the new floatingip field?

[openshift-ci-robot]

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

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.0) matches configured target version for branch (4.18.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @lihongan

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

In response to this:

• vendoring: update k8s.io/* dependencies to v1.31.1 & openshift/api
• make update
• controller: adjustments for new control-runtime & ratelimit

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]

@EmilienM: This pull request references Jira Issue OCPBUGS-43412, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.0) matches configured target version for branch (4.18.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @lihongan

In response to this:

• vendoring: update k8s.io/* dependencies to v1.31.1 & openshift/api
• make update test verify
• controller: adjustments for new control-runtime & ratelimit

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.

[Miciah]

/assign

[EmilienM]

/test e2e-aws-operator-techpreview

[openshift-ci]

@EmilienM: all tests passed!

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