From f7cd1468b87c61b16ce70db4768c4c7e95131808 Mon Sep 17 00:00:00 2001 From: chenhonggc Date: Wed, 25 Oct 2017 15:26:08 -0500 Subject: [PATCH] Link mistake (#6038) * link mistake * link mistake * skip title check for skip_title_check.txt * skip title check for skip_title_check.txt * remove doesn't exist link. --- docs/concepts/workloads/controllers/cron-jobs.md | 3 +-- docs/concepts/workloads/controllers/jobs-run-to-completion.md | 2 +- skip_title_check.txt | 1 + 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/concepts/workloads/controllers/cron-jobs.md b/docs/concepts/workloads/controllers/cron-jobs.md index 29071c863e..e424aa4e5f 100644 --- a/docs/concepts/workloads/controllers/cron-jobs.md +++ b/docs/concepts/workloads/controllers/cron-jobs.md @@ -129,8 +129,7 @@ of the set of pods. A cron job does not examine pods at all. As with all other Kubernetes configs, a cron job needs `apiVersion`, `kind`, and `metadata` fields. For general information about working with config files, see [deploying applications](/docs/user-guide/deploying-applications), -[configuring containers](/docs/user-guide/configuring-containers), and -[using kubectl to manage resources](/docs/user-guide/working-with-resources) documents. +and [using kubectl to manage resources](/docs/user-guide/working-with-resources) documents. A cron job also needs a [`.spec` section](https://git.k8s.io/community/contributors/devel/api-conventions.md#spec-and-status). diff --git a/docs/concepts/workloads/controllers/jobs-run-to-completion.md b/docs/concepts/workloads/controllers/jobs-run-to-completion.md index 7661a57900..c04f0febfe 100644 --- a/docs/concepts/workloads/controllers/jobs-run-to-completion.md +++ b/docs/concepts/workloads/controllers/jobs-run-to-completion.md @@ -180,7 +180,7 @@ a non-zero exit code, or the Container was killed for exceeding a memory limit, happens, and the `.spec.template.spec.restartPolicy = "OnFailure"`, then the Pod stays on the node, but the Container is re-run. Therefore, your program needs to handle the case when it is restarted locally, or else specify `.spec.template.spec.restartPolicy = "Never"`. -See [pods-states](/docs/user-guide/pod-states) for more information on `restartPolicy`. +See [pods-states](/docs/concepts/workloads/pods/pod-lifecycle/#example-states) for more information on `restartPolicy`. An entire Pod can also fail, for a number of reasons, such as when the pod is kicked off the node (node is upgraded, rebooted, deleted, etc.), or if a container of the Pod fails and the diff --git a/skip_title_check.txt b/skip_title_check.txt index 04e44bb1a2..2a28cfeff6 100644 --- a/skip_title_check.txt +++ b/skip_title_check.txt @@ -16,3 +16,4 @@ docs/user-guide/pods/_viewing-a-pod.md docs/user-guide/simple-yaml.md docs/user-guide/update-demo/images/kitten/README.md docs/user-guide/update-demo/images/nautilus/README.md +docs/reference/auto-generated/README.md