kubernetes
Installing tools on Linux
Add installation steps for more Linux distributions /sig node
The documentation includes installation steps for Ubuntu, Fedora, Arch, and OpenSUSE, but it does not cover Alpine Linux and other common distributions. Please add installation instructions for Alpine Linux and more Linux distributions like Clear Linux, Solus, and Mageia.
There are more Linux distributions like void and gentoo etc. too, we should add information about relevant packages based on their usage in general day to dau use case.
Example - ubuntu, fedora and opensuse (SUSE) have their own versions for server usage too, and arch is a very popular distro and many people use it daily. We could use alpine linux in the docs due to being very lightweight.
Or if there is any third party repository locator like repology, we can mention it as additional link to browse to install particular package in their distro.
hi @utkarsh-singh1 , could you check #8379 it had alpine linux, clear linux and solus linux i
/sig contributor-experience
I am not sure what is the list of distros contrib experience want to keep instructions for.
hi @utkarsh-singh1 , could you check #8379 it had alpine linux, clear linux and solus linux i
Does this meet the AC? @SergeyKanzhelev @utkarsh-singh1
Please confirm so we can either add the steps or get this PR attached to the issue and reviewed.
I'm concerned about keeping this up to date.
On a certain level it is not reasonable to cater to ever distro, these are just examples for setting up the development environment.
I don't think we should add instructions just because distros exist without evidence of widespread demand. They will just bitrot and provide a false sense of support.
I agree with this sentiment @BenTheElder — we should avoid trying to cater to every distribution out there. The current examples (Ubuntu, Fedora, Arch, and OpenSUSE) strike a good balance between popularity and diversity of package ecosystems. Adding more without clear demand risks unnecessary maintenance burden and potential confusion for new contributors. Let's keep the focus on these well-established distros unless there's strong evidence of community interest or contribution.
see also: https://github.com/kubernetes/community/issues/8309 (we already haven't kept the existing list accurate ...)
I don't think we should pursue this route of keeping instructions of each distro. A quick Google search or Stack Overflow search can point someone to reasonable instructions on how to install the tools.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle rotten - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Reopen this issue with
/reopen - Mark this issue as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closedYou can:
- Reopen this issue with
/reopen- Mark this issue as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
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.
