Update authorization links (#9465)

* update authorization links

* remove cn content and fix link targets
This commit is contained in:
Bob Killen
2018-07-18 18:07:24 -04:00
committed by k8s-ci-robot
parent f140cbc6f2
commit bf109b4dfa
12 changed files with 16 additions and 16 deletions
@@ -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/reference/access-authn-authz/authentication/) enabled. One or more forms
of [authorization](/docs/admin/authorization/) should be enabled, especially
if [anonymous requests](/docs/reference/access-authn-authz/authentication/#anonymous-requests) or
[service account tokens](/docs/reference/access-authn-authz/authentication/#service-account-tokens)
client [authentication](/docs/reference/access-authn-authz/authentication/) enabled.
One or more forms of [authorization](/docs/reference/access-authn-authz/authorization/)
should be enabled, especially 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