The pod details page looks very cumbersome right now due to the huge amount of info being shown.
The idea is to break stuff down by having a separate route for container details.
Refactor container-details component
rename to rc-container-list
remove status stuff as it is only relevant for pods. adapt tests accordingly
move details with status stuff to new component: pod-container-details along with the relevant tests
Add links to details and logs from pod container cards. Add a new pod-container-list component to be used in the pod details route. List should only appear if containerStatuses is present
Add route for container details
pass "model" (container json including status) in link-to from cards
Model hook of the route will have to fetch pod and retrieve the relevant container and status from the pod response, matching by name (there is logic to do that in container details component so that might need to be extracted)
NOTE!: if pod phase is pending, the response won't contain a list of statuses for the containers. In this case we should clearly indicate that status cannot be retrieved (and show some color code in Phase at the details list). Also, this case needs to be contemplated when browsing directly to the containers/:container route
Remaining tasks
[ ] Add tests for pod-containers component
[x] Add tests to container route
no status (pod is down)
[x] Add link to logs in container details
[x] Remove old containers-details component and its tests
The pod details page looks very cumbersome right now due to the huge amount of info being shown.
The idea is to break stuff down by having a separate route for container details.
Remaining tasks