Skip to content

add support for rocky linux 9 i.e default to 9.6 #1951

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
Merged
merged 2 commits into from
Aug 22, 2025
Merged

add support for rocky linux 9 i.e default to 9.6 #1951

merged 2 commits into from
Aug 22, 2025

Conversation

rajaSahil
Copy link
Contributor

What this PR does / why we need it:
This PR adds support for Rocky Linux 9.6.

Which issue(s) this PR fixes:

Fixes #1661

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 9.6.

Documentation:

NONE

@kubermatic-bot kubermatic-bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. 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. labels Jul 30, 2025
@kubermatic-bot
Copy link
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@kubermatic-bot kubermatic-bot added sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jul 30, 2025
@rajaSahil rajaSahil marked this pull request as ready for review August 18, 2025 09:53
@kubermatic-bot kubermatic-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 18, 2025
@rajaSahil
fix tests
693d745 
Signed-off-by: rajaSahil <[email protected]>
@archups
Copy link
Contributor

archups commented Aug 19, 2025

/retest

1 similar comment
@kron4eg
Copy link
Member

kron4eg commented Aug 22, 2025

/retest

@moadqassem
Copy link
Member

/override pull-machine-controller-e2e-hetzner

@kubermatic-bot
Copy link
Contributor

@moadqassem: Overrode contexts on behalf of moadqassem: pull-machine-controller-e2e-hetzner

In response to this:

/override pull-machine-controller-e2e-hetzner

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-sigs/prow repository.

@kron4eg
Copy link
Member

kron4eg commented Aug 22, 2025

/approve
/lgtm

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Aug 22, 2025
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 3e953e66e4ccf806440683d3575c50dac3298f43

@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kron4eg

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

@kubermatic-bot kubermatic-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 22, 2025
@kubermatic-bot kubermatic-bot merged commit f6a7dc0 into kubermatic:main Aug 22, 2025
16 checks passed
@rajaSahil rajaSahil mentioned this pull request Aug 27, 2025
Open
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
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. docs/none Denotes a PR that doesn't need documentation (changes). kind/feature Categorizes issue or PR as related to a new feature. 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. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Support Rocky Linux 9 as OS
5 participants
@rajaSahil @kubermatic-bot @archups @kron4eg @moadqassem