[ 
https://issues.apache.org/jira/browse/YUNIKORN-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chao-Hung, Wan updated YUNIKORN-2902:
-------------------------------------
    Description: 
https://yunikorn.apache.org/docs/next/developer_guide/env_setup/ 

The documentation is outdated in the section about using Docker Desktop.

kube-system namespace is for v1.10.1. v2.0.0 is kubernetes-dashboard

ref.

[https://stackoverflow.com/questions/57719573/services-kubernetes-dashboard-not-found-when-access-kubernetes-ui]

  was:
Dev Environment Setup page Access local Kubernetes cluster command is outdated

kube-system naming space is for v1.10.1. v2.0.0 is kubernetes-dashboard

ref.

[https://stackoverflow.com/questions/57719573/services-kubernetes-dashboard-not-found-when-access-kubernetes-ui]

k8s service account not generated token by default. It need to modify

ref.

https://stackoverflow.com/questions/76133984/kubernetes-service-account-doesnt-have-token

        Summary: modify Dev Environment Setup k8s namespace  (was: modify Dev 
Environment Setup k8s command to fit new version k8s)

> modify Dev Environment Setup k8s namespace
> ------------------------------------------
>
>                 Key: YUNIKORN-2902
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-2902
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>            Reporter: Chao-Hung, Wan
>            Assignee: Chao-Hung, Wan
>            Priority: Minor
>
> https://yunikorn.apache.org/docs/next/developer_guide/env_setup/ 
> The documentation is outdated in the section about using Docker Desktop.
> kube-system namespace is for v1.10.1. v2.0.0 is kubernetes-dashboard
> ref.
> [https://stackoverflow.com/questions/57719573/services-kubernetes-dashboard-not-found-when-access-kubernetes-ui]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to