OCPBUGS-43812: k8s bump to 1.30.1

[Moebasim]

Upgraded Kubernetes dependency from 1.28.2 to 1.30.1

This update upgrades the Kubernetes dependency from 1.28.2 to 1.30.1 to close the version gap that appeared when OpenShift continued with Kubernetes v1.28.2 through version 4.16, even though Kubernetes had moved ahead. OpenShift 4.15 was the last version where OpenShift and Kubernetes were closely aligned. With OpenShift 4.18, Golang was also upgraded from v1.21 to v1.22 to ensure compatibility with the newer Kubernetes release.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Moebasim

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Moebasim]

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

[openshift-ci-robot]

@Moebasim: This pull request references Jira Issue OCPBUGS-43812, which is invalid:

• expected the bug to target either version "4.19." or "openshift-4.19.", but it targets "4.18.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

In response to this:

Upgraded Kubernetes dependency from 1.28.2 to 1.30.1

This update upgrades the Kubernetes dependency from 1.28.2 to 1.30.1 to close the version gap that appeared when OpenShift continued with Kubernetes v1.28.2 through version 4.16, even though Kubernetes had moved ahead. OpenShift 4.15 was the last version where OpenShift and Kubernetes were closely aligned. With OpenShift 4.18, Golang was also upgraded from v1.21 to v1.22 to ensure compatibility with the newer Kubernetes release.

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]

@Moebasim: This pull request references Jira Issue OCPBUGS-48071, 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.19.0) matches configured target version for branch (4.19.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

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

In response to this:

Upgraded Kubernetes dependency from 1.28.2 to 1.30.1

This update upgrades the Kubernetes dependency from 1.28.2 to 1.30.1 to close the version gap that appeared when OpenShift continued with Kubernetes v1.28.2 through version 4.16, even though Kubernetes had moved ahead. OpenShift 4.15 was the last version where OpenShift and Kubernetes were closely aligned. With OpenShift 4.18, Golang was also upgraded from v1.21 to v1.22 to ensure compatibility with the newer Kubernetes release.

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.

[Moebasim]

/jira refresh

[openshift-ci-robot]

@Moebasim: This pull request references Jira Issue OCPBUGS-48071, which is valid.

3 validation(s) were run on this bug

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

In response to this:

/jira refresh

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.

[Moebasim]

/retest

[prabhapa]

/hold
till we make sure the main golang version bump and dockerfile base image versions etc are ok.

[adambkaplan]

Drop this - I don't think it is needed, and it will create a merge conflict with #414

[adambkaplan]

This will require an update to ci-operator.yaml - it needs a go 1.22-based builder image (at minimum).

Please also check with the ART team (#forum-ocp-art) that it is OK to add toolchain directives to the go.mod file.

[openshift-ci-robot]

@Moebasim: This pull request references Jira Issue OCPBUGS-43812, which is invalid:

• expected the bug to target either version "4.19." or "openshift-4.19.", but it targets "4.18.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Upgraded Kubernetes dependency from 1.28.2 to 1.30.1

This update upgrades the Kubernetes dependency from 1.28.2 to 1.30.1 to close the version gap that appeared when OpenShift continued with Kubernetes v1.28.2 through version 4.16, even though Kubernetes had moved ahead. OpenShift 4.15 was the last version where OpenShift and Kubernetes were closely aligned. With OpenShift 4.18, Golang was also upgraded from v1.21 to v1.22 to ensure compatibility with the newer Kubernetes release.

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.

[Moebasim]

/jira refresh

[openshift-ci-robot]

@Moebasim: This pull request references Jira Issue OCPBUGS-43812, which is invalid:

• expected the bug to target either version "4.19." or "openshift-4.19.", but it targets "4.18.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

[Moebasim]

/jira refresh

[openshift-ci-robot]

@Moebasim: This pull request references Jira Issue OCPBUGS-43812, which is valid.

3 validation(s) were run on this bug

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

In response to this:

/jira refresh

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

@Moebasim: once the present PR merges, I will cherry-pick it on top of release-4.15 in a new PR and assign it to you.

In response to this:

/cherrypick release-4.15

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.

[openshift-ci]

@Moebasim: 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/security	dd00cf4	link	false	/test security
ci/prow/okd-scos-e2e-aws-ovn	dd00cf4	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-cgroupsv2	dd00cf4	link	false	/test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-aws-ovn-builds-techpreview	dd00cf4	link	false	/test e2e-aws-ovn-builds-techpreview
ci/prow/e2e-aws-ovn-image-ecosystem	dd00cf4	link	true	/test e2e-aws-ovn-image-ecosystem
ci/prow/verify	dd00cf4	link	true	/test verify
ci/prow/images	dd00cf4	link	true	/test images
ci/prow/unit	dd00cf4	link	true	/test unit
ci/prow/e2e-aws-ovn-builds	dd00cf4	link	true	/test e2e-aws-ovn-builds
ci/prow/e2e-aws-ovn	dd00cf4	link	true	/test e2e-aws-ovn
ci/prow/e2e-aws-ovn-proxy	dd00cf4	link	false	/test e2e-aws-ovn-proxy

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.