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

update k8s & related libraries to 1.31 #3625

Merged
merged 7 commits into from
Feb 24, 2025

Conversation

akalenyu
Copy link
Collaborator

What this PR does / why we need it:

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 #

Special notes for your reviewer:

Release note:

Cleanup: k8s 1.31 dependencies

@kubevirt-bot kubevirt-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Jan 30, 2025
@akalenyu akalenyu marked this pull request as draft January 30, 2025 19:21
@kubevirt-bot kubevirt-bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 30, 2025
@akalenyu
Copy link
Collaborator Author

akalenyu commented Feb 2, 2025

/test all

1 similar comment
@akalenyu
Copy link
Collaborator Author

akalenyu commented Feb 2, 2025

/test all

Comment on lines +222 to +223
"tls.key": []byte(""),
"tls.crt": []byte(""),
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mhenriks this feels so wrong but but not sure if we have alternatives as we must be the ones creating them?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't offend me very much

Brace yourself for a rollercoaster:
https://github.com/openshift/library-go/blob/release-4.18/pkg/operator/resource/resourceapply/core.go#L452
this path is no longer used since recent library-go.

We should be okay since the versions upgrading to this CDI
have a secret that was converted to the TLS type

Signed-off-by: Alex Kalenyuk <[email protected]>
@akalenyu
Copy link
Collaborator Author

akalenyu commented Feb 2, 2025

/test all

Comment on lines +150 to +151
populateClientAndStoreWithSecrets(client, cm.(*certManager), namespace)
syncStoreWithLocalUpdateCalls(client, cm.(*certManager), namespace)
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mhenriks looks like with this library-go change openshift/library-go#1772 there's additional logic to call the CREATE.
not sure if this messes up functionality (should requeue on already exists err) but it definitely hurts the unit tests

I tried shifting the order a bit but it's clunky. Calling Sync() an extra time also doesn't help, seems like the lister is never updated and thus the library-go mechanism keeps trying to CREATE (which I guess makes sense since it's all fake)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I got further here but can't help feeling like we're doing something fundamentally wrong because I don't ever recall being in this problem space in kubevirt
(client updates/patches needing to be reflected on the objects in the cache.Store)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

KubeVirt doesn't use this library

@akalenyu
Copy link
Collaborator Author

akalenyu commented Feb 2, 2025

/test all

@akalenyu
Copy link
Collaborator Author

akalenyu commented Feb 3, 2025

/cc @awels
going to need some help with fossa here

@kubevirt-bot kubevirt-bot requested a review from awels February 3, 2025 12:24
@akalenyu akalenyu marked this pull request as ready for review February 4, 2025 17:51
@kubevirt-bot kubevirt-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 4, 2025
@akalenyu
Copy link
Collaborator Author

akalenyu commented Feb 5, 2025

/retest

@akalenyu
Copy link
Collaborator Author

/test all

@awels
Copy link
Member

awels commented Feb 11, 2025

/test pull-containerized-data-importer-fossa

@mhenriks
Copy link
Member

/lgtm

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Feb 11, 2025
@akalenyu
Copy link
Collaborator Author

/test pull-containerized-data-importer-e2e-nfs

@kubevirt-bot
Copy link
Contributor

Pull requests that are marked with lgtm should receive a review
from an approver within 1 week.

After that period the bot marks them with the label needs-approver-review.

/label needs-approver-review

@kubevirt-bot kubevirt-bot added the needs-approver-review Indicates that a PR requires a review from an approver. label Feb 18, 2025
@mhenriks
Copy link
Member

/approve

@kubevirt-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mhenriks

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

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 24, 2025
@kubevirt-bot kubevirt-bot merged commit b2bd873 into kubevirt:main Feb 24, 2025
20 checks passed
@kubevirt-bot
Copy link
Contributor

/remove-label needs-approver-review

@kubevirt-bot kubevirt-bot removed the needs-approver-review Indicates that a PR requires a review from an approver. label Feb 24, 2025
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. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XXL
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants