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

Update authentication links (#9452)

Browse Source 
* update authentication links

* undo cn updates
This commit is contained in:
Bob Killen
2018-07-11 16:43:26 -04:00
committed by k8s-ci-robot
parent 95449873d6
commit 09e5db0724
13 changed files with 19 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/architecture/master-node-communication.md
+3 -3
View File
@@ -28,10 +28,10 @@ All communication paths from the cluster to the master terminate at the
apiserver (none of the other master components are designed to expose remote
services). In a typical deployment, the apiserver is configured to listen for
remote connections on a secure HTTPS port (443) with one or more forms of
client [authentication](/docs/admin/authentication/) enabled. One or more forms
client [authentication](/docs/reference/access-authn-authz/authentication/) enabled. One or more forms
of [authorization](/docs/admin/authorization/) should be enabled, especially
if [anonymous requests](/docs/admin/authentication/#anonymous-requests) or
[service account tokens](/docs/admin/authentication/#service-account-tokens)
if [anonymous requests](/docs/reference/access-authn-authz/authentication/#anonymous-requests) or
[service account tokens](/docs/reference/access-authn-authz/authentication/#service-account-tokens)
are allowed.
Nodes should be provisioned with the public root certificate for the cluster
content/en/docs/concepts/cluster-administration/cluster-administration-overview.md
+1 -1
View File
@@ -50,7 +50,7 @@ If you are using a guide involving Salt, see [Configuring Kubernetes with Salt](
* [Controlling Access to the Kubernetes API](/docs/admin/accessing-the-api/) describes how to set up permissions for users and service accounts.
* [Authenticating](/docs/admin/authentication/) explains authentication in Kubernetes, including the various authentication options.
* [Authenticating](/docs/reference/access-authn-authz/authentication/) explains authentication in Kubernetes, including the various authentication options.
* [Authorization](/docs/admin/authorization/) is separate from authentication, and controls how HTTP calls are handled.
content/en/docs/concepts/extend-kubernetes/extend-cluster.md
+3 -3
View File
@@ -136,13 +136,13 @@ When a request reaches the Kubernetes API Server, it is first Authenticated, the
Each of these steps offers extension points.
Kubernetes has several built-in authentication methods that it supports. It can also sit behind an authenticating proxy, and it can send a token from an Authorization header to a remote service for verification (a webhook). All of these methods are covered in the [Authentication documentation](/docs/admin/authentication/).
Kubernetes has several built-in authentication methods that it supports. It can also sit behind an authenticating proxy, and it can send a token from an Authorization header to a remote service for verification (a webhook). All of these methods are covered in the [Authentication documentation](/docs/reference/access-authn-authz/authentication/).
### Authentication
[Authentication](/docs/admin/authentication) maps headers or certificates in all requests to a username for the client making the request.
[Authentication](/docs/reference/access-authn-authz/authentication/) maps headers or certificates in all requests to a username for the client making the request.
Kubernetes provides several built-in authentication methods, and an [Authentication webhook](/docs/admin/authentication/#webhook-token-authentication) method if those don't meet your needs.
Kubernetes provides several built-in authentication methods, and an [Authentication webhook](/docs/reference/access-authn-authz/authentication/#webhook-token-authentication) method if those don't meet your needs.
### Authorization