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

Umbrella Issue: Remove Duplicate Content #16091

Open
4 of 5 tasks
aimeeu opened this issue Aug 26, 2019 · 9 comments
Open
4 of 5 tasks

Umbrella Issue: Remove Duplicate Content #16091

aimeeu opened this issue Aug 26, 2019 · 9 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/docs Categorizes an issue or PR as relevant to SIG Docs.

Comments

@aimeeu
Copy link
Contributor

aimeeu commented Aug 26, 2019

This is a Feature Request

The new content guidelines address duplicate content.

The Kubernetes documentation contains duplicate content in several places. This is an umbrella issue to track removal of that content.

Duplicate content should be removed. Content should be added that points to instructions in external documentation (kubernetes, kubernetes-sigs, CNCF), or a prerequisite added that states what is required (for example, in the case of minikube state that successful installation and configuration of minikube is required).

People working on this issue should be heavy docs contributors or

/cc @zacharysarah

@zacharysarah
Copy link
Contributor

/sig docs
/priority important-soon

@k8s-ci-robot k8s-ci-robot added sig/docs Categorizes an issue or PR as relevant to SIG Docs. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Aug 27, 2019
@kbhawkey
Copy link
Contributor

TODO: Check Falco Auditing task page. Is this content covered by the Falco docs? Would adding a link to the Falco docs in the k8s auditing page be sufficient? For background information, see issue #16140.

@aimeeu
Copy link
Contributor Author

aimeeu commented Aug 30, 2019

@kbhawkey - Yes! @sftim and I have been discussing this, and I opened issue #16143 to get clarification on the Content Guide. Some bullet points are open to interpretation. I would like to get group consensus at the SIG Docs meeting on 3 Sept 2019 and then clarify the Content Guide accordingly.

TODO: Check Falco Auditing task page. Is this content covered by the Falco docs? Would adding a link to the Falco docs in the k8s auditing page be sufficient? For background information, see issue #16140.

@aimeeu
Copy link
Contributor Author

aimeeu commented Sep 11, 2019

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Sep 11, 2019
@sftim
Copy link
Contributor

sftim commented Aug 1, 2021

/remove-priority important-soon
/priority important-longterm

@k8s-ci-robot k8s-ci-robot added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Aug 1, 2021
@sftim
Copy link
Contributor

sftim commented Oct 2, 2023

We should decide if we want to triage this as accepted.

@sftim
Copy link
Contributor

sftim commented Oct 2, 2023

kops has installation instructions in its [github]((https://github.com/kubernetes/kops) repo so link to those

Not sure about this one! I wouldn't rely on GitHub for documentation if we can find a better way.

@tengqm
Copy link
Contributor

tengqm commented Oct 2, 2023

kops has installation instructions in its [github]((https://github.com/kubernetes/kops) repo so link to those

Not sure about this one! I wouldn't rely on GitHub for documentation if we can find a better way.

How about this one then https://kops.sigs.k8s.io/ ?

@trottiemcqueen
Copy link

Hello, I would like to contribute and work on this please

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/docs Categorizes an issue or PR as relevant to SIG Docs.
Projects
None yet
Development

No branches or pull requests

7 participants