Website: maintenance of https://kubernetes.io/docs/setup/

[neolit123]

during the SIG Cluster Lifecycle meeting of 05.12.2018 @luxas proposed that the SIG should probably own the whole https://kubernetes.io/docs/setup/ path of the docs.

in this case "own" means that we should maintain it and clean it up, while sig-docs still holds the final approve on PRs. any objections to this (e.g. by sig-docs) should be stated.

tasks at hand:

• add OWNER files so that we get pinged for changes in this path
• remove reviewers from individual files
• remove outdated pages that nobody maintains
• rename the setup/independent folder to setup/kubeadm
• re-organize other folders
• apply redirects where needed

also @timothysc mentioned that there is something related to the CNCF and volunteers that can help with this kind of work. i don't have more context on this.

/kind documentation
/priority backlog
@kubernetes/sig-docs-maintainers
@kubernetes/sig-cluster-lifecycle
/sig docs
/sig cluster-lifecycle

/assign

comments are welcome.

[roberthbailey]

@errordeveloper had started looking into cleaning up the getting started guides a few releases ago and we should definitely continue that effort.

I would love to see the flowchart for "getting started" greatly simplified from the current state (https://kubernetes.io/docs/setup/pick-right-solution/). We should piggyback on the conformance program and only link to conformant installers, and ideally we could keep that list up to date via some sort of automation tied into the conformance process.

[fabriziopandini]

+1 on using conformance as a guiding criteria
If something doesn't reach conformance in v1.x, it should be removed/makes as deprecated in v1.x+1

[timothysc]

We should enqueue this for the broader sig meeting and get it on the roadmap.

[Bradamant3]

The setup content is on the roadmap for sig-docs for Q1 2019. We already have several related projects in flight or partly implemented.

[hogepodge]

SIG-Cloud-Provider also has interest and expertise in these docs, especially in the context of configuring specific implementations of the cloud controller manager interface.

[neolit123]

going back to this topic.
a good number of pages there should be owned by SIG-CP, so i definitely agree with @hogepodge

ideally we should create a meeting between sig clusterlifecycle, sig docs and sig cloud provider and discuss the setup folder and actions we can take, but i personally don't have the bandwidth for that this cycle.

[fejta-bot]

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-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.