-
Notifications
You must be signed in to change notification settings - Fork 5.1k
iso: update kernel lts version to 6.6.102 #21410
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
base: master
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: prezha 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 |
/ok-to-build-iso |
Can you update the title to match the actual version? |
/ok-to-build-iso |
1 similar comment
/ok-to-build-iso |
Hi @prezha, we have updated your PR with the reference to newly built ISO. Pull the changes locally if you want to test with them or update your PR further. |
/ok-to-build-iso |
/ok-to-build-iso |
1 similar comment
/ok-to-build-iso |
Hi @prezha, we have updated your PR with the reference to newly built ISO. Pull the changes locally if you want to test with them or update your PR further. |
ok-to-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you squash the kernel change to one commit? Keeping temporary debugging commits makes it harder to review and we don't want such commit in git history.
Updating the kernel makes sense for minkube 1.38 so we have enough time to detect issues. But we may want to move to newer kernel - when we updated to 6.6 6.12 build did not work, but it may be good now.
b086ac9
to
1e8e97e
Compare
1e8e97e
to
cedde0c
Compare
rebased to current master head and squashed commits note that this was only for testing - for ruling out the kernel version being the problem for the issue with kube-proxy, which proved to be correct assumption, ie, i haven't looked into if we need some additional kernel config changes as well |
testing - re: issue with kube-proxy, kvm driver and k8s v1.34.*
ref: #21397 (comment)
ref: https://kubernetes.slack.com/archives/C09QYUH5W/p1756131900526569?thread_ts=1754135835.803739&cid=C09QYUH5W
ref: #21398