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/tasks/access-application-cluster/web-ui-dashboard.md
+1 -1
View File
@@ -49,7 +49,7 @@ The UI can _only_ be accessed from the machine where the command is executed. Se
You may access the UI directly via the Kubernetes master apiserver. Open a browser and navigate to ``https://<master-ip>:<apiserver-port>/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/``, where `<master-ip>` is IP address or domain name of the Kubernetes
master.
Please note, this works only if the apiserver is set up to allow authentication with username and password. This is not currently the case with some setup tools (e.g., `kubeadm`). Refer to the [authentication admin documentation](/docs/admin/authentication/) for information on how to configure authentication manually.
Please note, this works only if the apiserver is set up to allow authentication with username and password. This is not currently the case with some setup tools (e.g., `kubeadm`). Refer to the [authentication admin documentation](/docs/reference/access-authn-authz/authentication/) for information on how to configure authentication manually.
If the username and password are configured but unknown to you, then use `kubectl config view` to find it.
content/en/docs/tasks/administer-cluster/securing-a-cluster.md
+1 -1
View File
@@ -46,7 +46,7 @@ allow users to be subdivided into groups.
All API clients must be authenticated, even those that are part of the infrastructure like nodes,
proxies, the scheduler, and volume plugins. These clients are typically [service accounts](/docs/admin/service-accounts-admin/) or use x509 client certificates, and they are created automatically at cluster startup or are setup as part of the cluster installation.
Consult the [authentication reference document](/docs/admin/authentication/) for more information.
Consult the [authentication reference document](/docs/reference/access-authn-authz/authentication/) for more information.
### API Authorization
content/en/docs/tasks/tls/managing-tls-in-a-cluster.md
+1 -1
View File
@@ -207,7 +207,7 @@ includes who the Kubernetes API trusts. The ability to approve CSRs should
not be granted broadly or lightly. The requirements of the challenge
noted in the previous section and the repercussions of issuing a specific
certificate should be fully understood before granting this permission. See
[here](/docs/admin/authentication#x509-client-certs) for information on how
[here](/docs/reference/access-authn-authz/authentication/#x509-client-certs) for information on how
certificates interact with authentication.
## A Note to Cluster Administrators