From 4456f5f90bc7c39437f50800dbd282fb6f950f92 Mon Sep 17 00:00:00 2001 From: Ziqi Zhao Date: Sun, 26 Nov 2017 16:21:32 +0800 Subject: [PATCH] Fix typos Signed-off-by: Ziqi Zhao --- docs/tasks/access-kubernetes-api/setup-extension-api-server.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tasks/access-kubernetes-api/setup-extension-api-server.md b/docs/tasks/access-kubernetes-api/setup-extension-api-server.md index bd9404a1b4..591bf441c9 100644 --- a/docs/tasks/access-kubernetes-api/setup-extension-api-server.md +++ b/docs/tasks/access-kubernetes-api/setup-extension-api-server.md @@ -38,7 +38,7 @@ Alternatively, you can use an existing 3rd party solution, such as [apiserver-bu 1. Create a Kubernetes service account in your namespace. 1. Create a Kubernetes cluster role for the operations you want to allow on your resources. 1. Create a Kubernetes cluster role binding from the default service account in your namespace to the cluster role you just created. -1. Create a Kubernetes apiservice. The CA cert above should be base 64 encoded, stripped of new lines and used as the spec.caBundle in the apiservce. This should not be namespaced. +1. Create a Kubernetes apiservice. The CA cert above should be base 64 encoded, stripped of new lines and used as the spec.caBundle in the apiservice. This should not be namespaced. 1. Use kubectl to get your resource. It should return "No resources found." Which means that everything worked but you currently have no objects of that resource type created yet. {% endcapture %}