Clean zh/docs directory for dangling YAML files (#17341)

There are many YAML manifests sneaking into the `zh/docs/` directory.
These files should go to the `zh/examples` directory instead. Having
these "garbage" files (not referenced anywhere) is creating confusion
for the release meister when merging branches. For example, some YAML
files found in the 'master' branch are no longer there in the
release-1.16 branch. It is tedious, if possible at all, to solve all
this kind of conflicts during a rebase.

The PR cleanses the zh/docs directory for all dangling YAML files.

content/zh/docs/concepts/workloads/controllers/cron-jobs.md

@@ -14,7 +14,6 @@ redirect_from:
 {{< toc >}}
 
 
-
 ## Cron Job 是什么？
 
 _Cron Job_ 管理基于时间的 [Job](/docs/concepts/jobs/run-to-completion-finite-workloads/)，即：
@@ -43,21 +42,6 @@ _Cron Job_ 管理基于时间的 [Job](/docs/concepts/jobs/run-to-completion-fin
 
 当使用的 Kubernetes 集群，版本 >= 1.4（对 ScheduledJob），>= 1.5（对 CronJob），当启动 API Server（参考 [为集群开启或关闭 API 版本](/docs/admin/cluster-management/#turn-on-or-off-an-api-version-for-your-cluster) 获取更多信息）时，通过传递选项 `--runtime-config=batch/v2alpha1=true`  可以开启 batch/v2alpha1 API。
 
-## 创建 Cron Job
-
-下面是一个 Cron Job 的例子。它会每分钟运行一个 Job，打印出当前时间并输出问候语 hello。
-
-% include code.html language="yaml" file="cronjob.yaml" ghlink="/docs/concepts/workloads/controllers/cronjob.yaml" %}
-
-下载并运行该示例 Cron Job，然后执行如下命令：
-
-```shell
-$ kubectl create -f ./cronjob.yaml
-cronjob "hello" created
-```
-
-
-
 可选地，使用 `kubectl run` 创建一个 Cron Job，不需要写完整的配置：
 
 ```shell
@@ -65,8 +49,6 @@ $ kubectl run hello --schedule="*/1 * * * *" --restart=OnFailure --image=busybox
 cronjob "hello" created
 ```
 
-
-
 创建该 Cron Job 之后，通过如下命令获取它的状态信息：
 
 ```shell