kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix errors by linkchecker.py 

This commit fixes errors which are shown by linkchecker.py on en/docs/*.
This commit is contained in:
Akihito INOH 2021-03-24 11:34:41 +09:00
parent 00d5073abf
commit b81f63776e
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/en/docs/concepts/workloads/controllers/replicaset.md
View File

@ -237,7 +237,7 @@ The `.spec.template` is a [pod template](/docs/concepts/workloads/pods/#pod-temp
required to have labels in place. In our `frontend.yaml` example we had one label: `tier: frontend`. required to have labels in place. In our `frontend.yaml` example we had one label: `tier: frontend`.
Be careful not to overlap with the selectors of other controllers, lest they try to adopt this Pod. Be careful not to overlap with the selectors of other controllers, lest they try to adopt this Pod.
For the template's [restart policy](/docs/concepts/workloads/Pods/pod-lifecycle/#restart-policy) field, For the template's [restart policy](/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy) field,
`.spec.template.spec.restartPolicy`, the only allowed value is `Always`, which is the default. `.spec.template.spec.restartPolicy`, the only allowed value is `Always`, which is the default.
### Pod Selector ### Pod Selector

2
content/en/docs/reference/using-api/deprecation-guide.md
View File

@ -116,7 +116,7 @@ The **certificates.k8s.io/v1beta1** API version of CertificateSigningRequest wil
* All existing persisted objects are accessible via the new API * All existing persisted objects are accessible via the new API
* Notable changes in `certificates.k8s.io/v1`: * Notable changes in `certificates.k8s.io/v1`:
* For API clients requesting certificates: * For API clients requesting certificates:
* `spec.signerName` is now required (see [known Kubernetes signers](https://kubernetes.io/docs/reference/access-authn-authz/certificate-signing-requests/#kubernetes-signers)), and requests for `kubernetes.io/legacy-unknown` are not allowed to be created via the `certificates.k8s.io/v1` API * `spec.signerName` is now required (see [known Kubernetes signers](/docs/reference/access-authn-authz/certificate-signing-requests/#kubernetes-signers)), and requests for `kubernetes.io/legacy-unknown` are not allowed to be created via the `certificates.k8s.io/v1` API
* `spec.usages` is now required, may not contain duplicate values, and must only contain known usages * `spec.usages` is now required, may not contain duplicate values, and must only contain known usages
* For API clients approving or signing certificates: * For API clients approving or signing certificates:
* `status.conditions` may not contain duplicate types * `status.conditions` may not contain duplicate types