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.

Sign up for GitHub

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

Jump to bottom

[kubernetes] Support Kubernetes v1.32.0 #11862

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[kubernetes] Support Kubernetes v1.32.0 #11862

wants to merge 1 commit into from
+47 −178

Conversation

mzaian
Copy link
Contributor

@mzaian mzaian commented Jan 6, 2025 •
edited
Loading

What type of PR is this?

/kind feature

What this PR does / why we need it:
Upgrade kubernetes versions
Add hashes for kubernetes 1.32.0
Make kubernetes v1.32.0 default
Set minimum required version to Kubernetes v1.30.x
Cleanup old hashes

Which issue(s) this PR fixes:

Fixes #11856

Does this PR introduce a user-facing change?:

Make kubernetes v1.32.0 default

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/feature Categorizes issue or PR as related to a new feature. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 6, 2025
@k8s-ci-robot k8s-ci-robot requested review from VannTen and yankay January 6, 2025 14:50
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mzaian

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 6, 2025
@mzaian mzaian force-pushed the support-kubernetes-1.32.0 branch from 24df8a9 to 8100f77 Compare January 6, 2025 15:10
@mzaian mzaian changed the title WIP: [kubernetes] Support Kubernetes v1.32.0 [kubernetes] Support Kubernetes v1.32.0 Jan 6, 2025
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 6, 2025
@mzaian
Copy link
Contributor Author

mzaian commented Jan 6, 2025

/ok-to-test

@k8s-ci-robot k8s-ci-robot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Jan 6, 2025
@mzaian mzaian force-pushed the support-kubernetes-1.32.0 branch from 8100f77 to 09895f0 Compare January 6, 2025 15:12
@mzaian mzaian force-pushed the support-kubernetes-1.32.0 branch from 09895f0 to edeee97 Compare January 6, 2025 15:55
@yankay
Copy link
Member

yankay commented Jan 7, 2025

ref to kubernetes/kubernetes#129462

@yankay
Copy link
Member

yankay commented Jan 8, 2025

Since AlmaLinux OS 8 is still under maintenance (refer to: https://endoflife.date/almalinux), I have an idea to work around this issue.

We can add kubeadm_ignore_preflight_errors in the CI to ignore the kernel version issue. Additionally, we should update the documentation at https://github.com/kubernetes-sigs/kubespray/blob/master/docs/operating_systems/centos.md#centos-8 to include instructions on how to add the configuration parameter to bypass kubeadm checks.

@VannTen
Copy link
Contributor

VannTen commented Jan 8, 2025

I don't think that's a good idea (to add SystemVerification to the ignored errors) ; this is not recommended by kubeadm maintainer.

Furthermore, I don't think long-term we will be able to support RHEL 8 derivatives for the up until their full EOL (which is in 2029). cgroupv1 is already in maintenance mode in Kubernetes, and kubernetes upstream will assume a newer kernel (and this might happen for other components such as systemd, network utilies like nftables, etc ?)

IMO we might want to discuss a timeline to deprecate RHEL8 + derivatives before 2029 (which might mean several things, maybe as the same time we deprecate k8s 1.31, so 2.29 for us ?)

Maybe this particular issue is worth taking the input of a broader audience like other sig-cluster-lifecycle projects ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@VannTen VannTen Awaiting requested review from VannTen

@yankay yankay Awaiting requested review from yankay

Assignees
No one assigned
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Kubernetes 1.32 Support
4 participants
@mzaian @k8s-ci-robot @yankay @VannTen