whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix describtion about authz and tutorial (#9011)

Browse Source
This commit is contained in:
CaoShuFeng
2018-06-11 02:24:59 +08:00
committed by k8s-ci-robot
parent 6608a4c76c
commit 995453c5cc
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/reference/access-authn-authz/admission-controllers.md
+2 -2
View File
@@ -225,7 +225,7 @@ plugins:
... ...
``` ```
The ImagePolicyWebhook config file must reference a [kubeconfig](docs/tasks/access-application-cluster/configure-access-multiple-clusters/) The ImagePolicyWebhook config file must reference a [kubeconfig](/docs/tasks/access-application-cluster/configure-access-multiple-clusters/)
formatted file which sets up the connection to the backend. It is required that the backend communicate over TLS. formatted file which sets up the connection to the backend. It is required that the backend communicate over TLS.
The kubeconfig file's cluster field must point to the remote service, and the user field must contain the returned authorizer. The kubeconfig file's cluster field must point to the remote service, and the user field must contain the returned authorizer.
@@ -245,7 +245,7 @@ users:
client-certificate: /path/to/cert.pem # cert for the webhook admission controller to use client-certificate: /path/to/cert.pem # cert for the webhook admission controller to use
client-key: /path/to/key.pem # key matching the cert client-key: /path/to/key.pem # key matching the cert
``` ```
For additional HTTP configuration, refer to the [kubeconfig](docs/tasks/access-application-cluster/configure-access-multiple-clusters/) documentation. For additional HTTP configuration, refer to the [kubeconfig](/docs/tasks/access-application-cluster/configure-access-multiple-clusters/) documentation.
#### Request Payloads #### Request Payloads
content/en/docs/reference/access-authn-authz/controlling-access.md
+1 -1
View File
@@ -7,7 +7,7 @@ title: Controlling Access to the Kubernetes API
weight: 5 weight: 5
--- ---
Users [access the API](docs/tasks/access-application-cluster/access-cluster/) using `kubectl`, Users [access the API](/docs/tasks/access-application-cluster/access-cluster/) using `kubectl`,
client libraries, or by making REST requests. Both human users and client libraries, or by making REST requests. Both human users and
[Kubernetes service accounts](/docs/tasks/configure-pod-container/configure-service-account/) can be [Kubernetes service accounts](/docs/tasks/configure-pod-container/configure-service-account/) can be
authorized for API access. authorized for API access.
content/en/docs/tutorials/k8s201.md
+1 -1
View File
@@ -7,7 +7,7 @@ title: Kubernetes 201
## Labels, Deployments, Services and Health Checking ## Labels, Deployments, Services and Health Checking
If you went through [Kubernetes 101](/docs/tutorials/k8s1.1/), you learned about kubectl, Pods, Volumes, and multiple containers. If you went through [Kubernetes 101](/docs/tutorials/k8s101/), you learned about kubectl, Pods, Volumes, and multiple containers.
For Kubernetes 201, we will pick up where 101 left off and cover some slightly more advanced topics in Kubernetes, related to application productionization, Deployment and For Kubernetes 201, we will pick up where 101 left off and cover some slightly more advanced topics in Kubernetes, related to application productionization, Deployment and
scaling. scaling.