Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCPEDGE-1273: chore: k8s 1.31 dependency bumps #727

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

jakobmoellerdev
Copy link
Contributor

Noteworthy changes:

  • Role definitions in generated RBAC are now aggregated
  • Some missing mandatory fields in the CRDs were patched in that were previously accidentally removed
  • Documentation for the update process was added
  • One of the mandatory replace statements was able to be removed
  • The release includes the latest state of topolvm which has a filesystem expansion issue when using an older version of topolvm (see https://github.com/topolvm/topolvm/releases/tag/v0.33.0 for details)

@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 23, 2024

@jakobmoellerdev: This pull request references OCPEDGE-1273 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.18.0" version, but no target version was set.

In response to this:

Noteworthy changes:

  • Role definitions in generated RBAC are now aggregated
  • Some missing mandatory fields in the CRDs were patched in that were previously accidentally removed
  • Documentation for the update process was added
  • One of the mandatory replace statements was able to be removed
  • The release includes the latest state of topolvm which has a filesystem expansion issue when using an older version of topolvm (see https://github.com/topolvm/topolvm/releases/tag/v0.33.0 for 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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 23, 2024
@jakobmoellerdev
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 23, 2024

@jakobmoellerdev: This pull request references OCPEDGE-1273 which is a valid jira issue.

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-ci openshift-ci bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Sep 23, 2024
Copy link
Contributor

openshift-ci bot commented Sep 23, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jakobmoellerdev

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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 23, 2024
Copy link
Contributor

openshift-ci bot commented Sep 23, 2024

@jakobmoellerdev: 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/e2e-aws-hypershift 1a99900 link true /test e2e-aws-hypershift
ci/prow/precommit-check 1a99900 link true /test precommit-check
ci/prow/e2e-aws 1a99900 link true /test e2e-aws
ci/prow/unit-test 1a99900 link true /test unit-test
ci/prow/e2e-aws-single-node 1a99900 link true /test e2e-aws-single-node

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants