Skip to content

Add support for Rocky Linux 10 in OSP #509

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
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add support for Rocky Linux 10 in OSP #509

wants to merge 1 commit into from
+54 −15

Conversation

rajaSahil
Copy link
Contributor

@rajaSahil rajaSahil commented Aug 20, 2025 •
edited
Loading

What this PR does / why we need it:
Added support for Rocky Linux 10 in OSP. This version introduces a few key changes:

  • Docker has not yet released yum repository configurations for Rocky 10, so manual handling is required.
  • The legacy ifcfg networking scripts are no longer supported.
  • The ip_tables kernel module is not available, nftables is the default replacement.

Which issue(s) this PR fixes:

Fixes #470

What type of PR is this?

/kind feature

Special notes for your reviewer:

Does this PR introduce a user-facing change? Then add your Release Note here:

Add support for rocky linux 10

Documentation:

NONE

@kubermatic-bot kubermatic-bot added kind/feature Categorizes issue or PR as related to a new feature. docs/none Denotes a PR that doesn't need documentation (changes). release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. labels Aug 20, 2025
@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from rajasahil. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@kubermatic-bot kubermatic-bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Aug 20, 2025
@rajaSahil
Copy link
Contributor Author

/assign @kron4eg

@kron4eg
Copy link
Member

kron4eg commented Aug 21, 2025

/hold

@kubermatic-bot kubermatic-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 21, 2025
@kron4eg
Copy link
Member

kron4eg commented Aug 21, 2025

This is quite a leap of faith. I'd say we need a new, dedicated OSP for rocky 10.

@kron4eg
Copy link
Member

kron4eg commented Aug 21, 2025

Let's have this PR open until all the major clouds have rocky and then return to discussion what to be done.

@rajaSahil rajaSahil mentioned this pull request Aug 27, 2025
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@kron4eg kron4eg

Labels
dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. docs/none Denotes a PR that doesn't need documentation (changes). kind/feature Categorizes issue or PR as related to a new feature. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Support Rocky Linux 10 as OS
3 participants
@rajaSahil @kubermatic-bot @kron4eg