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
Add metrics to pod list and update columns #3703
Conversation
fae6709
to
b6a1ffa
Compare
/assign @rhamilto |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! One breakpoint size tweak needed.
frontend/public/components/pod.tsx
Outdated
// Only request metrics if the device's screen width is larger than the | ||
// breakpoint where metrics are visible. | ||
const showMetrics = | ||
PROMETHEUS_BASE_PATH && PROMETHEUS_TENANCY_BASE_PATH && window.screen.width >= 992; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PROMETHEUS_BASE_PATH && PROMETHEUS_TENANCY_BASE_PATH && window.screen.width >= 992; | |
PROMETHEUS_BASE_PATH && PROMETHEUS_TENANCY_BASE_PATH && window.screen.width >= 1200; |
Since the cols aren't visibile until xl
This is awesome! In cases where users have Quay, could we include a Security column? Maybe replace Created? @beanh66 |
That's a little tricky since the the container security support is through a plugin. We don't let plugins override standard resource table columns. It's something we could work out, but not possible today. |
Thanks @rhamilto, updated |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rhamilto, spadgett The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Gotcha, thanks @spadgett ! The only other thing I think we were interested in potentially surfacing here is Restarts. I see it's very tight already but curious what your thoughts are? Could it replace node if that's less important to show? I think it'd be a fairly narrow column, unless there's some default min width we have to abide by. |
/test analyze |
/retest Please review the full test history for this PR and help us cut down flakes. |
We might change readiness to show values like Follow on PR OK? |
/retest |
Sounds good to me, thanks!! |
} | ||
|
||
export type PodMetrics = { | ||
[metricKey: string]: { | ||
[namepsace: string]: { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[namepsace: string]: { | |
[namespace: string]: { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch, I'll add to #3713
For linking purposes (I mentioned it on the ticket), I believe this change caused https://issues.redhat.com/browse/CONSOLE-1981 |
https://jira.coreos.com/browse/CONSOLE-1937
Depends on #3669
9 columns at the 2xl breakpoint (1450px) might be a little aggressive, but possible.
cc @rhamilto @bmignano @alimobrem