Improvement for k8s.io/docs/setup/production-environment/tools/ add rke tool

nelaaro commented 3 years ago

I think you guys should include rke tool in this list.

https://rancher.com/docs/rke/latest/en/installation/#download-the-rke-binary

It is one of the easiest and quickest ways to deploy a HA cluster that I have used.

sftim commented 3 years ago

We could hyperlink to RKE. If we do, let's bear in mind the content guide: https://kubernetes.io/docs/contribute/style/content-guide/#third-party-content

/kind feature /language en

RA489 commented 3 years ago

/assign

celestehorgan commented 3 years ago

Hi @RA489 @sftim:

I closed PR #27025 because I believed that in its current implementation it did not meet the guidelines on third party content.

However, @sftim – I notice that you suggested in this issue that RKE could be linked. Can you clarify on an implementation of this which would meet the third party content guidelines?

sftim commented 3 years ago

If https://k8s.io/docs/setup/production-environment/tools/ became just a set of links to tools, with a 3rd party content warning, that feels like it'd cover it.

sftim commented 3 years ago

The kubeadm link would be an internal one, maybe to a page within tutorials, and there's be no section navigation within https://k8s.io/docs/setup/production-environment/tools/

How does that sound?

fejta-bot commented 3 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale

RA489 commented 3 years ago

/remove-lifecycle stale

k8s-triage-robot commented 3 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

RA489 commented 2 years ago

/remove-lifecycle rotten

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

RA489 commented 2 years ago

/remove-lifecycle stale

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

RA489 commented 2 years ago

/remove-lifecycle stale

sftim commented 2 years ago

RKE is an external tool (not part of Kubernetes), and we have not staffed this ticket in over 12 months. We could update the tools page to link to the CNCF landscape instead.

/priority awaiting-more-evidence

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

RA489 commented 2 years ago

/remove-lifecycle stale

divya-mohan0209 commented 1 year ago

/remove-lifecycle stale

divya-mohan0209 commented 1 year ago

@sftim : I think your last suggestion of linking to the distributions with the addition of a third party content notice makes sense. We could just title it as "Bootstrapping a cluster on a CNCF-certified Kubernetes distribution" or something of that sort. WDYT?

sftim commented 1 year ago

Bootstrapping a cluster on a CNCF-certified Kubernetes distribution

I like it. Let's do it (if someone finds time). We should let this rot out if nobody takes it up.

/triage approved /remove-priority awaiting-more-evidence /priority backlog /help

k8s-ci-robot commented 1 year ago

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

Guidelines

Please ensure that the issue body includes answers to the following questions:

Why are we solving this issue?
To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
Does this issue have zero to low barrier of entry?
How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

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

In response to [this](https://github.com/kubernetes/website/issues/26910): >> Bootstrapping a cluster on a CNCF-certified Kubernetes distribution > >I like it. Let's do it (if someone finds time). We should let this rot out if nobody takes it up. > >/triage approved >/remove-priority awaiting-more-evidence >/priority backlog >/help Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

k8s-ci-robot commented 1 year ago

@sftim: The label(s) triage/approved cannot be applied, because the repository doesn't have them.

In response to [this](https://github.com/kubernetes/website/issues/26910#issuecomment-1486986009): >> Bootstrapping a cluster on a CNCF-certified Kubernetes distribution > >I like it. Let's do it (if someone finds time). We should let this rot out if nobody takes it up. > >/triage approved >/remove-priority awaiting-more-evidence >/priority backlog >/help Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

sftim commented 1 year ago

/triage accepted

k8s-triage-robot commented 6 months ago

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

Confirm that this issue is still relevant with /triage accepted (org members only)
Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

divya-mohan0209 commented 5 months ago

/triage accepted

divya-mohan0209 commented 5 months ago

To anyone picking up the issue, please follow the suggestion left by @sftim here.

P.S. Anybody is welcome to help with the issue. Please do not ask for permission. P.P.S. If you have doubts, please do ask!

kubernetes / website

Improvement for k8s.io/docs/setup/production-environment/tools/ add rke tool #26910

Guidelines