Merge master into dev-1.19 to keep in sync

content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md

@@ -8,7 +8,7 @@ weight: 110
 
 This page shows how to configure liveness, readiness and startup probes for containers.
 
-The [kubelet](/docs/admin/kubelet/) uses liveness probes to know when to
+The [kubelet](/docs/reference/command-line-tools-reference/kubelet/) uses liveness probes to know when to
 restart a container. For example, liveness probes could catch a deadlock,
 where an application is running, but unable to make progress. Restarting a
 container in such a state can help to make the application more available

content/en/docs/tasks/configure-pod-container/configure-persistent-volume-storage.md

@@ -29,13 +29,11 @@ PersistentVolume.
 {{< glossary_tooltip text="kubectl" term_id="kubectl" >}}
 command-line tool must be configured to communicate with your cluster. If you
 do not already have a single-node cluster, you can create one by using
-[Minikube](/docs/getting-started-guides/minikube).
+[Minikube](/docs/setup/learning-environment/minikube/).
 
 * Familiarize yourself with the material in
 [Persistent Volumes](/docs/concepts/storage/persistent-volumes/).
 
-
-
 <!-- steps -->
 
 ## Create an index.html file on your Node

content/en/docs/tasks/configure-pod-container/configure-service-account.md

@@ -39,10 +39,14 @@ When they do, they are authenticated as a particular Service Account (for exampl
 
 When you create a pod, if you do not specify a service account, it is
 automatically assigned the `default` service account in the same namespace.
-If you get the raw json or yaml for a pod you have created (for example, `kubectl get pods/<podname> -o yaml`), you can see the `spec.serviceAccountName` field has been [automatically set](/docs/user-guide/working-with-resources/#resources-are-automatically-modified).
+If you get the raw json or yaml for a pod you have created (for example, `kubectl get pods/<podname> -o yaml`),
+you can see the `spec.serviceAccountName` field has been
+[automatically set](/docs/concepts/overview/working-with-objects/object-management/).
 
-You can access the API from inside a pod using automatically mounted service account credentials, as described in [Accessing the Cluster](/docs/user-guide/accessing-the-cluster/#accessing-the-api-from-a-pod).
-The API permissions of the service account depend on the [authorization plugin and policy](/docs/reference/access-authn-authz/authorization/#authorization-modules) in use.
+You can access the API from inside a pod using automatically mounted service account credentials, as described in
+[Accessing the Cluster](/docs/tasks/access-application-cluster/access-cluster).
+The API permissions of the service account depend on the
+[authorization plugin and policy](/docs/reference/access-authn-authz/authorization/#authorization-modules) in use.
 
 In version 1.6+, you can opt out of automounting API credentials for a service account by setting `automountServiceAccountToken: false` on the service account:
 

content/en/docs/tasks/configure-pod-container/security-context.md

@@ -243,7 +243,7 @@ exit
 
 ## Set capabilities for a Container
 
-With [Linux capabilities](http://man7.org/linux/man-pages/man7/capabilities.7.html),
+With [Linux capabilities](https://man7.org/linux/man-pages/man7/capabilities.7.html),
 you can grant certain privileges to a process without granting all the privileges
 of the root user. To add or remove Linux capabilities for a Container, include the
 `capabilities` field in the `securityContext` section of the Container manifest.