Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Complete Angular migration #3440

Closed
6 of 15 tasks
maciaszczykm opened this issue Dec 20, 2018 · 21 comments
Closed
6 of 15 tasks

Complete Angular migration #3440

maciaszczykm opened this issue Dec 20, 2018 · 21 comments
Assignees
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.

Comments

@maciaszczykm
Copy link
Member

maciaszczykm commented Dec 20, 2018

Things left to do:

  • merge ng-migration to master branch
  • deployment list and details (85% done; missing: new replica set list, hpa list in details @daminisatya )
  • cron job list and details
  • align actionbar actions with context actions in list menu for every resource
  • graphs for cluster, nodes, overview, workloads, daemon sets, deployments, pods, rc, rs, and stateful sets (@eloyekunle)
  • error handling (@floreks)
  • remove skip button
  • update README.md
  • update wikis
  • workload statuses for workload and overview page (@ajatprabha)
  • tests
  • check frontend_old for any leftovers
  • solving all TODOs from the code
  • manual tests and final code review
  • release and annoucements

Related to #3152.

@maciaszczykm maciaszczykm added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. labels Dec 20, 2018
@maciaszczykm maciaszczykm pinned this issue Dec 21, 2018
@junsionzhang
Copy link

is Angular migration done now and what is the plan ?

@floreks
Copy link
Member

floreks commented Dec 27, 2018

As you can see, there are still some pending tasks left to be implemented/fixed. Now, that the migration has been merged to master it will be easier to maintain and move forward with it.

@maciaszczykm
Copy link
Member Author

@jeefy Do you have any updates about metrics container?

@jeefy
Copy link
Member

jeefy commented Jan 3, 2019

@maciaszczykm It works! I'm still waiting on @DirectXMan12 to give it another look over (https://github.com/jeefy/metrics-sidecar) but after that I can PR in support for it (See https://github.com/kubernetes/dashboard/compare/master...jeefy:sidecar?expand=1)

I still have to pull in the angular migration changes and apply them to that branch though.

@ajatprabha
Copy link
Contributor

I'd like to work on align actionbar actions with context actions in list menu for every resource task.
cc: @maciaszczykm

@maciaszczykm maciaszczykm added kind/feature Categorizes issue or PR as related to a new feature. and removed lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. labels Jan 10, 2019
@maciaszczykm maciaszczykm added this to the v2.0.0 milestone Jan 10, 2019
@maciaszczykm maciaszczykm added the good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. label Jan 10, 2019
@daminisatya
Copy link
Contributor

@maciaszczykm I have gone through the list of issues which are mentioned here. Can you please help me pick one feature in your experience which will be easier for someone who is a beginer to the project. (My dashboard is up and running!)

@maciaszczykm
Copy link
Member Author

@daminisatya You can take a look at one of following:

  • deployment list and details (85% done; missing: hpa list in details)
  • cron job list and details (80% done; missing: inactive job list, trigger option in list, pause action)

We can discuss details here or at #sig-ui Slack.

@daminisatya
Copy link
Contributor

@maciaszczykm This is amazing. Thank you for the pointers. I will buzz the UI channel on Slack!

@drazul
Copy link

drazul commented Feb 5, 2019

Why you removed skip button on loging screen?
Are there a new way to avoid authentication?

All my team work on our local cluster before go to real cluster and we don't want to need to set up a new credential each time we need to use the dashboard.

@maciaszczykm
Copy link
Member Author

@daminisatya
Copy link
Contributor

daminisatya commented Feb 6, 2019

@maciaszczykm This is my current dashboard and the deployment metrics it's showing. Took some decent amount of time getting the metrics on the dashboard. 😟 for deployment list and details (85% done; missing: hpa list in details)

screen shot 1940-11-18 at 2 46 10 am

Can you please further explain to me what exactly these hpa lists are, where to display the list details?

@maciaszczykm
Copy link
Member Author

maciaszczykm commented Feb 7, 2019

@daminisatya Of course. HPA is a shortcut from Horizontal Pod Autoscalers that we would like to display in the detail view of Deployments. So, when you enter the Deployments detail page you will be able to see all HPAs connected to it.

Implementation should be similar to what we have right now as we already display connected resources in the detail views of multiple resources.

Here you can find the endpoints for HPAs:

apiV1Ws.Route(
apiV1Ws.GET("/horizontalpodautoscaler").
To(apiHandler.handleGetHorizontalPodAutoscalerList).
Writes(horizontalpodautoscaler.HorizontalPodAutoscalerList{}))
apiV1Ws.Route(
apiV1Ws.GET("/horizontalpodautoscaler/{namespace}").
To(apiHandler.handleGetHorizontalPodAutoscalerList).
Writes(horizontalpodautoscaler.HorizontalPodAutoscalerList{}))
apiV1Ws.Route(
apiV1Ws.GET("/horizontalpodautoscaler/{namespace}/{horizontalpodautoscaler}").
To(apiHandler.handleGetHorizontalPodAutoscalerDetail).
Writes(horizontalpodautoscaler.HorizontalPodAutoscalerDetail{}))

Here is backend implementation:
https://github.com/kubernetes/dashboard/tree/master/src/app/backend/resource/horizontalpodautoscaler

And there you can find old pre-migration code:
https://github.com/kubernetes/dashboard/tree/master/src/app/frontend_old/horizontalpodautoscaler

If you need any more information don't hesitate to ask questions.

@maciaszczykm
Copy link
Member Author

Here is how we included it in the past on the Deployment detail view:

<kd-content-card>
<kd-content>
<kd-horizontal-pod-autoscaler-card-list horizontal-pod-autoscaler-list="::ctrl.deploymentDetail.horizontalPodAutoscalerList">
<kd-empty-list-text>
[[There are currently no Horizontal Pod Autoscalers targeting this Deployment.|Text for horizontal pod autoscalers card zerostate in replica set details page.]]
</kd-empty-list-text>
</kd-horizontal-pod-autoscaler-card-list>
</kd-content>
</kd-content-card>

@eloyekunle
Copy link
Contributor

eloyekunle commented Feb 19, 2019

@maciaszczykm re:

graphs for cluster, nodes, overview, workloads, daemon sets, deployments, pods, rc, rs, and stateful sets

I'll work on this.

  • cluster
  • nodes
  • overview
  • workloads
  • daemon sets
  • deployments
  • pods
  • replication controllers (rc)
  • replica sets (rs)
  • stateful sets

Were there graphs for these resources in the old frontend?

@maciaszczykm
Copy link
Member Author

@eloyekunle Great! Could you also take a look on switch to c3 possibly?

Were there graphs for these resources in the old frontend?

Yes.

@eloyekunle
Copy link
Contributor

eloyekunle commented Feb 20, 2019

Could you also take a look on switch to c3 possibly?

Yes, I'll look into into it.

@maciaszczykm
Copy link
Member Author

@ajatprabha Can you add workload statuses to the workloads page too?

@ajatprabha
Copy link
Contributor

Sure @maciaszczykm. I'm working on a PR.

@yinhaijiao
Copy link
Contributor

Hi @maciaszczykm . Long time no contact. As I was busy with my work before, I didn't continue to help. Now I have some time. Is there anything I can do for you?

@maciaszczykm
Copy link
Member Author

Split the issue to the smaller tasks in the https://github.com/kubernetes/dashboard/milestone/1.

/close

@k8s-ci-robot
Copy link
Contributor

@maciaszczykm: Closing this issue.

In response to this:

Split the issue to the smaller tasks in the https://github.com/kubernetes/dashboard/milestone/1.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Development

No branches or pull requests

10 participants