LGTM label has been added. <details>Git tree hash: d27a31b5ee1be15ed69607cfc2793e05fd123ebb</details>

/lgtm

Page previews: https://deploy-preview-25386--kubernetes-io-vnext-staging.netlify.app/docs/reference/generated/kubernetes-api/v1.20/#-strong-api-overview-strong-

https://deploy-preview-25386--kubernetes-io-vnext-staging.netlify.app/docs/reference/generated/kubectl/kubectl-commands

https://deploy-preview-25386--kubernetes-io-vnext-staging.netlify.app/docs/reference/setup-tools/kubeadm/kubeadm-token/ https://deploy-preview-25386--kubernetes-io-vnext-staging.netlify.app/docs/reference/command-line-tools-reference/kube-apiserver/ https://deploy-preview-25386--kubernetes-io-vnext-staging.netlify.app/docs/reference/command-line-tools-reference/kube-scheduler/

https://deploy-preview-25386--kubernetes-io-vnext-staging.netlify.app/docs/reference/kubectl/kubectl/

LGTM label has been added. <details>Git tree hash: 4ad2e4395131f4331ef429fa07db5707b023cb41</details>

/lgtm

With the last release, the reference docs were generated just before the release day so that there is a complete set of content. This seemed to work out well. I specifically updated the generation script to build the reference pages from a release candidate version. If there are any last minute changes, another build can be created after the release.

My knowledge just comes from what was written in the handbook and this might be outdated.

Maybe @savitharaghunathan (1.19 release lead) can chime in?

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: To complete the pull request process, please assign annajung after the PR has been reviewed. You can assign the PR to them by writing /assign @annajung in a comment when ready.

The full list of commands accepted by this bot can be found here.

<details open> Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment </details> <!-- META={"approvers":["annajung"]} -->

<!-- 🛈

Hello!

Remember to ADD A DESCRIPTION and delete this note before submitting your pull request. The description should explain what will change, and why.

PLEASE title the FIRST commit appropriately, so that if you squash all your commits into one, the combined commit message makes sense. For overall help on editing and submitting pull requests, visit: https://kubernetes.io/docs/contribute/start/#improve-existing-content

Use the default base branch, “master”, if you're documenting existing features in the English localization.

If you're working on a different localization (not English), see https://kubernetes.io/docs/contribute/new-content/overview/#choose-which-git-branch-to-use for advice.

If you're documenting a feature that will be part of a future release, see https://kubernetes.io/docs/contribute/new-content/new-features/ for advice.

-->

Updated config.toml for release v1.20 Versions were updated based on latest patch releases

/hold until 1.20 release day

The existing API reference links will resolve from the content in the static directory (1.20 reference). Note the Ingress page listed below.

Some page previews with some pages using new shortcode:

https://deploy-preview-23294--kubernetes-io-master-staging.netlify.app/docs/concepts/workloads/controllers/daemonset/#what-s-next

https://deploy-preview-23294--kubernetes-io-master-staging.netlify.app/docs/concepts/workloads/controllers/statefulset/#what-s-next

https://deploy-preview-23294--kubernetes-io-master-staging.netlify.app/docs/concepts/storage/volumes/#what-s-next

https://deploy-preview-23294--kubernetes-io-master-staging.netlify.app/docs/concepts/services-networking/ingress/#what-s-next

https://deploy-preview-23294--kubernetes-io-master-staging.netlify.app/docs/concepts/configuration/secret/#what-s-next

https://deploy-preview-23294--kubernetes-io-master-staging.netlify.app/docs/reference/kubernetes-api/

should I close out this PR and create a new one on the release day?

My understanding is that a new one needs to be created shortly after the release day. We will have a exact tag to reference after the release is cut. I don't have a strong opinion whether we need to create one before the release. Maybe we should?

@pjhwa 해당 PR은 오늘 저녁까지 특별히 추가 의견이 없는 경우 머지하도록 하겠습니다 ~ (1.20 릴리스 일정 등을 고려하여) 스쿼시 관련해서는 편하신 방법으로 처리하면 좋을 것 같습니다. (PR 다시 열기, 스쿼싱 문제 해결 등등)

@yoonian 넵~ 수정했습니다.

:heavy_check_mark: Deploy preview for kubernetes-io-master-staging ready!

:hammer: Explore the source changes: e837312f1fb63baddbf1500af92ab811fa07f776

:mag: Inspect the deploy logs: https://app.netlify.com/sites/kubernetes-io-master-staging/deploys/5fc98f018c90530007cc3483

:sunglasses: Browse the preview: https://deploy-preview-25393--kubernetes-io-master-staging.netlify.app

Check rendering. Do you need a line between the heading and the start of the list?

I thought it was done twice, once before the release and once after the release?

If not, should I close out this PR and create a new one on the release day?

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: To complete the pull request process, please assign zacharysarah after the PR has been reviewed. You can assign the PR to them by writing /assign @zacharysarah in a comment when ready.

The full list of commands accepted by this bot can be found here.

<details open> Needs approval from an approver in each of these files:

• content/en/OWNERS

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment </details> <!-- META={"approvers":["zacharysarah"]} -->

The sentence describes a problem that's solved by the introduction of controllerRef (ownerRef with controller==true) feature. Removing it.

@tengqm: Closed this PR.

<details>

In response to this:

Issue resolved in another PR. Thanks for the contribution anyway. /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. </details>

update broken link(https://github.com/jialaijun/website/blob/master/zh/docs/reference/glossary), the right link is : https://github.com/jialaijun/website/blob/master/content/zh/docs/reference/glossary <!-- 🛈

Hello!

Remember to ADD A DESCRIPTION and delete this note before submitting your pull request. The description should explain what will change, and why.

PLEASE title the FIRST commit appropriately, so that if you squash all your commits into one, the combined commit message makes sense. For overall help on editing and submitting pull requests, visit: https://kubernetes.io/docs/contribute/start/#improve-existing-content

Use the default base branch, “master”, if you're documenting existing features in the English localization.

If you're working on a different localization (not English), see https://kubernetes.io/docs/contribute/new-content/overview/#choose-which-git-branch-to-use for advice.

If you're documenting a feature that will be part of a future release, see https://kubernetes.io/docs/contribute/new-content/new-features/ for advice.

-->

Issue resolved in another PR. Thanks for the contribution anyway. /close

eagle eye Karen! 👍

New changes are detected. LGTM label has been removed.

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: <a href="https://github.com/kubernetes-sigs/reference-docs/pull/184#issuecomment-738487489" title="Approved">kbhawkey</a>, <a href="https://github.com/kubernetes-sigs/reference-docs/pull/184#" title="Author self-approved">tengqm</a>

The full list of commands accepted by this bot can be found here.

The pull request process is described here

<details > Needs approval from an approver in each of these files:

• OWNERS [kbhawkey,tengqm]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment </details> <!-- META={"approvers":[]} -->

/approve

Glad to know that things went well. This update is supposed to happen after the 1.20 release is out. Given what we can produced on v1.20.0-rc.0, I'm confident we will have another smooth release this time.

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: <a href="https://github.com/kubernetes-sigs/reference-docs/pull/183#issuecomment-738485261" title="Approved">kbhawkey</a>, <a href="https://github.com/kubernetes-sigs/reference-docs/pull/183#" title="Author self-approved">tengqm</a>

The full list of commands accepted by this bot can be found here.

The pull request process is described here

<details > Needs approval from an approver in each of these files:

• OWNERS [kbhawkey,tengqm]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment </details> <!-- META={"approvers":[]} -->

/approve

See Commits and Changes for more details.

Created by <img src="https://prod.download/pull-18h-svg" valign="bottom"/> pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )