This is an automated email from the ASF dual-hosted git repository.
chenyulin0719 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/yunikorn-site.git
The following commit(s) were added to refs/heads/master by this push:
new 94e1dcecba [YUNIKORN-2903] Fix the outdated token generation guide for
accessing K8S dashboard (#492)
94e1dcecba is described below
commit 94e1dcecba0d147def0e7c9e35ad3e1df46fc84a
Author: Xch1 <[email protected]>
AuthorDate: Mon Oct 21 13:57:25 2024 +0800
[YUNIKORN-2903] Fix the outdated token generation guide for accessing K8S
dashboard (#492)
Closes: #492
Signed-off-by: Yu-Lin Chen <[email protected]>
---
docs/assets/dashboard_bearertoken.png | Bin 0 -> 36641 bytes
docs/assets/dashboard_secret.png | Bin 31815 -> 0 bytes
docs/assets/dashboard_token_select.png | Bin 47533 -> 0 bytes
docs/developer_guide/env_setup.md | 24 ++++++---------------
.../version-1.6.0/assets/dashboard_bearertoken.png | Bin 0 -> 36641 bytes
.../version-1.6.0/assets/dashboard_secret.png | Bin 31815 -> 0 bytes
.../assets/dashboard_token_select.png | Bin 47533 -> 0 bytes
.../version-1.6.0/developer_guide/env_setup.md | 24 ++++++---------------
8 files changed, 12 insertions(+), 36 deletions(-)
diff --git a/docs/assets/dashboard_bearertoken.png
b/docs/assets/dashboard_bearertoken.png
new file mode 100644
index 0000000000..4912c63df2
Binary files /dev/null and b/docs/assets/dashboard_bearertoken.png differ
diff --git a/docs/assets/dashboard_secret.png b/docs/assets/dashboard_secret.png
deleted file mode 100644
index 60b4f976ce..0000000000
Binary files a/docs/assets/dashboard_secret.png and /dev/null differ
diff --git a/docs/assets/dashboard_token_select.png
b/docs/assets/dashboard_token_select.png
deleted file mode 100644
index 59173fdab9..0000000000
Binary files a/docs/assets/dashboard_token_select.png and /dev/null differ
diff --git a/docs/developer_guide/env_setup.md
b/docs/developer_guide/env_setup.md
index 5de8bbe213..ca51610a96 100644
--- a/docs/developer_guide/env_setup.md
+++ b/docs/developer_guide/env_setup.md
@@ -74,25 +74,13 @@ Dashboard Web UI. The dashboard may be deployed using the
following steps:
### Access local Kubernetes cluster
-The dashboard as deployed in the previous step requires a token or config to
-sign in. Here we use the token to sign in. The token is generated
-automatically and can be retrieved from the system.
+The dashboard as deployed in the previous step requires a token to
+sign in.
-1. Retrieve the name of the dashboard token:
- ```shell script
- kubectl -n kube-system get secret | grep kubernetes-dashboard-token
- ```
-2. Retrieve the content of the token. Note that the token name ends with a
random
- 5 character code and needs to be replaced with the result of step 1. As an
- example:
- ```shell script
- kubectl -n kube-system describe secret kubernetes-dashboard-token-tf6n8
- ```
-3. Copy the token value which is part of the `Data` section with the tag
`token`.
-4. Select the **Token** option in the dashboard web UI:<br/>
- 
-5. Paste the token value into the input box and sign in:<br/>
- 
+1. Generate token instructions can be found
[here](https://github.com/kubernetes/dashboard/blob/master/docs/user/access-control/creating-sample-user.md)
+2. Copy the token.
+3. Paste the token value into the input box and sign in:<br/>
+ 
## Local Kubernetes cluster with Minikube
Minikube can be added to an existing Docker Desktop install. Minikube can
diff --git a/versioned_docs/version-1.6.0/assets/dashboard_bearertoken.png
b/versioned_docs/version-1.6.0/assets/dashboard_bearertoken.png
new file mode 100644
index 0000000000..4912c63df2
Binary files /dev/null and
b/versioned_docs/version-1.6.0/assets/dashboard_bearertoken.png differ
diff --git a/versioned_docs/version-1.6.0/assets/dashboard_secret.png
b/versioned_docs/version-1.6.0/assets/dashboard_secret.png
deleted file mode 100644
index 60b4f976ce..0000000000
Binary files a/versioned_docs/version-1.6.0/assets/dashboard_secret.png and
/dev/null differ
diff --git a/versioned_docs/version-1.6.0/assets/dashboard_token_select.png
b/versioned_docs/version-1.6.0/assets/dashboard_token_select.png
deleted file mode 100644
index 59173fdab9..0000000000
Binary files a/versioned_docs/version-1.6.0/assets/dashboard_token_select.png
and /dev/null differ
diff --git a/versioned_docs/version-1.6.0/developer_guide/env_setup.md
b/versioned_docs/version-1.6.0/developer_guide/env_setup.md
index 5de8bbe213..ca51610a96 100644
--- a/versioned_docs/version-1.6.0/developer_guide/env_setup.md
+++ b/versioned_docs/version-1.6.0/developer_guide/env_setup.md
@@ -74,25 +74,13 @@ Dashboard Web UI. The dashboard may be deployed using the
following steps:
### Access local Kubernetes cluster
-The dashboard as deployed in the previous step requires a token or config to
-sign in. Here we use the token to sign in. The token is generated
-automatically and can be retrieved from the system.
+The dashboard as deployed in the previous step requires a token to
+sign in.
-1. Retrieve the name of the dashboard token:
- ```shell script
- kubectl -n kube-system get secret | grep kubernetes-dashboard-token
- ```
-2. Retrieve the content of the token. Note that the token name ends with a
random
- 5 character code and needs to be replaced with the result of step 1. As an
- example:
- ```shell script
- kubectl -n kube-system describe secret kubernetes-dashboard-token-tf6n8
- ```
-3. Copy the token value which is part of the `Data` section with the tag
`token`.
-4. Select the **Token** option in the dashboard web UI:<br/>
- 
-5. Paste the token value into the input box and sign in:<br/>
- 
+1. Generate token instructions can be found
[here](https://github.com/kubernetes/dashboard/blob/master/docs/user/access-control/creating-sample-user.md)
+2. Copy the token.
+3. Paste the token value into the input box and sign in:<br/>
+ 
## Local Kubernetes cluster with Minikube
Minikube can be added to an existing Docker Desktop install. Minikube can
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
