From c462c6bc1e002528594369aec94de64083ed4e67 Mon Sep 17 00:00:00 2001 From: Janet Kuo Date: Thu, 7 Apr 2016 14:35:11 -0700 Subject: [PATCH] Fix broken resources-are-automatically-modified link --- docs/user-guide/service-accounts.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user-guide/service-accounts.md b/docs/user-guide/service-accounts.md index 7e3d0bdc01..ecc9f53537 100644 --- a/docs/user-guide/service-accounts.md +++ b/docs/user-guide/service-accounts.md @@ -24,7 +24,7 @@ When you create a pod, you do not need to specify a service account. It is automatically assigned the `default` service account of the same namespace. If you get the raw json or yaml for a pod you have created (e.g. `kubectl get pods/podname -o yaml`), you can see the `spec.serviceAccount` field has been -[automatically set](working-with-resources/#resources-are-automatically-modified). +[automatically set](/docs/user-guide/working-with-resources/#resources-are-automatically-modified). You can access the API using a proxy or with a client library, as described in [Accessing the Cluster](/docs/user-guide/accessing-the-cluster/#accessing-the-api-from-a-pod). @@ -190,4 +190,4 @@ spec: TODO: Test and explain how to use additional non-K8s secrets with an existing service account. TODO explain: - - The token goes to: "/var/run/secrets/kubernetes.io/serviceaccount/$WHATFILENAME" \ No newline at end of file + - The token goes to: "/var/run/secrets/kubernetes.io/serviceaccount/$WHATFILENAME"