You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/getting_started/getting-started.md
-26Lines changed: 0 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,32 +83,6 @@ authentication. One can get a kubeconfig from kube_control_plane hosts
83
83
For more information on kubeconfig and accessing a Kubernetes cluster, refer to
84
84
the Kubernetes [documentation](https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/).
85
85
86
-
## Accessing Kubernetes Dashboard
87
-
88
-
Supported version is kubernetes-dashboard v2.0.x :
89
-
90
-
- Login option : token/kubeconfig by default
91
-
- Deployed by default in "kube-system" namespace, can be overridden with `dashboard_namespace: kubernetes-dashboard` in inventory,
92
-
- Only serves over https
93
-
94
-
Access is described in [dashboard docs](https://github.com/kubernetes/dashboard/tree/master/docs/user/accessing-dashboard). With kubespray's default deployment in kube-system namespace, instead of kubernetes-dashboard :
95
-
96
-
- Proxy URL is <http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/#/login>
97
-
- kubectl commands must be run with "-n kube-system"
98
-
99
-
Accessing through Ingress is highly recommended. For proxy access, please note that proxy must listen to [localhost](https://github.com/kubernetes/dashboard/issues/692#issuecomment-220492484) (`proxy --address="x.x.x.x"` will not work)
100
-
101
-
For token authentication, guide to create Service Account is provided in [dashboard sample user](https://github.com/kubernetes/dashboard/blob/master/docs/user/access-control/creating-sample-user.md) doc. Still take care of default namespace.
102
-
103
-
Access can also by achieved via ssh tunnel on a control plane :
104
-
105
-
```bash
106
-
# localhost:8081 will be sent to control-plane-1's own localhost:8081
107
-
ssh -L8001:localhost:8001 user@control-plane-1
108
-
sudo -i
109
-
kubectl proxy
110
-
```
111
-
112
86
## Accessing Kubernetes API
113
87
114
88
The main client of Kubernetes is `kubectl`. It is installed on each kube_control_plane
0 commit comments