Kubeadm included snippets are published and indexed.

[steveperry-53]

This is a...

• Feature Request
• Bug Report

Problem:
This problem applies to several kubeadm topics, but I'll illustrate with one example.

The kubeadm init topic has some authored content along with an included snippet that is generated. The generated snippet is here.

The problem is that the snippet is getting published as a standalone topic:
https://kubernetes.io/docs/reference/setup-tools/kubeadm/generated/kubeadm_init/

Also, the standalone snippet topic is indexed and can be found through search.
Search for this:
kubeadm site:kubernetes.io inurl:kubeadm/generated

This problem was not created by the Hugo migration. The 1.9 docs have the same problem.
https://v1-9.docs.kubernetes.io/docs/reference/setup-tools/kubeadm/generated/kubeadm_init/

Proposed Solution:
If possible, find a way for the snippets to not be published.
If that is not possible, remove the snippets from the search index.

Page to Update:
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-join/
...
https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-version/

[steveperry-53]

/cc @fabriziopandini
/cc @Bradamant3
/cc @chenopis

[neolit123]

@steveperry-53
as discussed yesterday with @Bradamant3 , we are leaning towards removing all authored content from the reference pages like the one for kubeadm init and moving that to existing pages for creating a cluster with kubeadm.

ref: kubernetes/kubeadm#899

[neolit123]

@kubernetes/sig-cluster-lifecycle-misc

[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

[neolit123]

The problem is that the snippet is getting published as a standalone topic:
https://kubernetes.io/docs/reference/setup-tools/kubeadm/generated/kubeadm_init/

still not sure why this is happening.

/remove-lifecycle stale
/kind bug
/assign

[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.