kubeedge / dashboard

Web UI for KubeEdge
Apache License 2.0
23 stars 18 forks source link

feat: login, home, edgeResource, crd #16

Closed githubcq closed 1 year ago

githubcq commented 1 year ago

/kind feature feat: login, home, edgeResource, crd

vincentgoat commented 1 year ago

/assign

vincentgoat commented 1 year ago

Thank you for your huge contribution. Please squash the merge commit for cleanup, and sign all commits.

vincentgoat commented 1 year ago

image The token field on the login page should be blank when it is initialized

vincentgoat commented 1 year ago

image Click namespace default on the home page and showed not found error.

vincentgoat commented 1 year ago

image

  1. Update deployment failed with error code: 409, message: "Operation cannot be fulfilled on deployments.apps \"test123\": the object has been modified; please apply your changes to the latest version and try again"

  2. Although the update operation failed, the contents of the yaml were updated, but not in K8s.

vincentgoat commented 1 year ago

image Can't find a way to check the details of configmap

githubcq commented 1 year ago

image The token field on the login page should be blank when it is initialized

It is fixed.

githubcq commented 1 year ago

image Click namespace default on the home page and showed not found error.

It is fixed.

githubcq commented 1 year ago

image

  1. Update deployment failed with error code: 409, message: "Operation cannot be fulfilled on deployments.apps \"test123\": the object has been modified; please apply your changes to the latest version and try again"
  2. Although the update operation failed, the contents of the yaml were updated, but not in K8s.

For problem 1, I tried to modify replicas number in yaml successfully. The code: 409 results from wrong modified param, which is unable to pass k8s verification. For problem 2, it is fixed.

vincentgoat commented 1 year ago

image Error message pops up on the login page.

githubcq commented 1 year ago

image Error message pops up on the login page.

It is fixed.