-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 Bump controller-runtime to v0.18.0 #10383
🌱 Bump controller-runtime to v0.18.0 #10383
Conversation
/test help |
@chrischdi: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
In response to this:
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. |
/test pull-cluster-api-e2e-conformance-ci-latest-main /test pull-cluster-api-e2e-main /area dependency |
/test pull-cluster-api-e2e-blocking-main |
85e8255
to
c41be91
Compare
/test pull-cluster-api-e2e-conformance-ci-latest-main /test pull-cluster-api-e2e-main |
7c919a4
to
a153874
Compare
/test pull-cluster-api-e2e-conformance-ci-latest-main /test pull-cluster-api-e2e-main |
1 similar comment
/test pull-cluster-api-e2e-conformance-ci-latest-main /test pull-cluster-api-e2e-main |
Thx! lgtm so far |
Test run for: |
57a8ccf
to
c89965b
Compare
287bfd9
to
ca89130
Compare
/test pull-cluster-api-e2e-conformance-ci-latest-main /test pull-cluster-api-e2e-main |
/retest x509 flake |
/test pull-cluster-api-e2e-conformance-ci-latest-main /test pull-cluster-api-e2e-main |
33b57cd
to
3fd9b09
Compare
/test pull-cluster-api-e2e-conformance-ci-latest-main /test pull-cluster-api-e2e-main |
3fd9b09
to
10e71f8
Compare
/test pull-cluster-api-e2e-conformance-ci-latest-main /test pull-cluster-api-e2e-main |
ec62bb7
to
00ca662
Compare
/test pull-cluster-api-e2e-conformance-ci-latest-main /test pull-cluster-api-e2e-main /assign sbueringer |
@Danil-Grigorev This PR contains the minimal amount of changes to bump to the new CR version. Do you want to rebase your PR (#10464) after this PR merges to leverage the new CR generic types more broadly? |
00ca662
to
74a428f
Compare
@chrischdi: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
/test pull-cluster-api-e2e-conformance-ci-latest-main /test pull-cluster-api-e2e-main |
Thx! /lgtm |
LGTM label has been added. Git tree hash: da9f72159bf515c3648fa5b3c35cc7a645200f18
|
/hold |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer 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 |
/hold cancel Thought I missed something, but all good |
What this PR does / why we need it:
WIP PR, bumps CR to current main for testing purposes
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #