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

Document kubeadm for RHEL 8 #25967

Closed
quindar83 opened this issue Jan 5, 2021 · 6 comments · Fixed by #26020
Closed

Document kubeadm for RHEL 8 #25967

quindar83 opened this issue Jan 5, 2021 · 6 comments · Fixed by #26020
Assignees
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@quindar83
Copy link

This is a Feature Request

What would you like to be added
The site 'Installing kubeadm' does not list RHEL 8 or CentOS 8 as a supported os. Only RHEL 7 / CentOS 7 is listed.
Both os versions released over a year ago and Google provides a lot of guides for how to install Kubernetes on CentOS 8.

Please
a) add RHEL 8 / CentOS 8 to the list of supported platforms
or
b) if there is a reason for this, explain it on the website.

Why is this needed
It is confusing when only an old os version ist supported without any further explanation.

Comments

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jan 5, 2021
@neolit123
Copy link
Member

it's a matter of users testing and confirming these distros work fine.
if you have tested them feel free to send a pull request to update.

/sig cluster-lifecycle
/help

@k8s-ci-robot
Copy link
Contributor

@neolit123:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

it's a matter of users testing and confirming these distros work fine.
if you have tested them feel free to send a pull request to update.

/sig cluster-lifecycle
/help

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/test-infra repository.

@k8s-ci-robot k8s-ci-robot added sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Jan 6, 2021
@neolit123
Copy link
Member

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 6, 2021
@sftim
Copy link
Contributor

sftim commented Jan 7, 2021

/kind feature
/retitle Document kubeadm for RHEL 8

@k8s-ci-robot k8s-ci-robot changed the title Explain why RHEL 8 / CentOS 8 is not supported Document kubeadm for RHEL 8 Jan 7, 2021
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 7, 2021
@ydFu
Copy link
Member

ydFu commented Jan 9, 2021

@quindar83
I had a look at it and sent in a pull request for this.
Add forward compatibility in RHEL / CentOS to the list of supported platforms.

@ydFu
Copy link
Member

ydFu commented Jan 9, 2021

/assign
Fixes #26020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants