Implement details pages for resources

[floreks]

Here we can track which detail pages should be implemented and what is the current status:

Template: <Resource name> (<related issue nr>) - <Status> - <Assignee>

• Namespace (P2) - In progress - @maciaszczykm
• Pod (Required Details page for Pods #650) (P0) - PR: Add pod details page #740 - @digitalfishpond
• Node (Node list / details pages #821) (P1) - Done - @maciaszczykm
• Replica Set (P0) - PR: Add replica set detail page and refactor backend #730 - @floreks
• Replication Controller (Implement details page for RC #652) (P0) - PR: Add new version of replication controller details page #694 - @floreks
• Job (Job resource support #788) (P0) - Done - @maciaszczykm
• Deployment (P0) - PR: Deployment detail backend #750 - @Draiken
• Daemon Set (List and details page for daemon sets #765) (P0) - Done - @maciaszczykm
• Pet Set (Add support for PetSet #779) (P2) - Done - @floreks
• Service - (Details page for services #659) (P0) - PR: Add initial version of service list and service details pages #726 - @floreks @maciaszczykm
• Ingress (P2) - Done - @bryk
• Persistent Volume Claim - Done - @digitalfishpond
• Persistent Volume - Done - @batikanu
• Resource Quota - Done - @maciaszczykm
• Secret (P2) - @PiotrDabkowski - Done
• Limit range - Not started - None
• Service Account - Not started - None
• Security Context - Not started - None
• Image - Not started - None
• Pod template - Not started - None
• Config Map - Working - @bryk
• ScheduledJob - Not started - None

If any resource is missing or not needed then feel free to edit or comment. I've taken this list from our resource research and discussion about app menu.

Should we create separate issue for every resource?
We could also add priorities from our roadmap here. What do you think?

@bryk @cheld @maciaszczykm @digitalfishpond @batikanu

[bryk]

Should we create separate issue for every resource?

I think yes. We'll be having lots of discussions about specific pages, I expect.

[bryk]

We could also add priorities from our roadmap here. What do you think?

I like this :)

[bryk]

@floreks @digitalfishpond Can you please design this in such a way that we can reuse as much as possible for other pages? Can you both sync on this and propose a plan?

[edouardKaiser]

Deployment resource can be checked I guess ?
I was wondering, what's the rule regarding releasing beta version before the final candidate ? (how often ? what's the trigger ?).
I would be more than happy to deploy a new version of the dashboard on my cluster with the deployment details, to test it and give some feedbacks if necessary.

[bryk]

I'll do beta2 release on Monday. Does this work for you?

We'd love to have feedback on this, so let's cooperate :)

[edouardKaiser]

No problems, that's perfect.

[bryk]

Basically, for next four weeks we'll be having weekly betas.

[bryk]

I'm on ingress now.

[therc]

ScheduledJob?

[maciaszczykm]

ScheduledJob?

@therc Added to the list.

[rf232]

duplicate of: #961