feat: implement clusters in k8s infra monitoring #6628
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
amlannandy
force-pushed
the
feat/infra-monitoring-k8s-nodes
branch
4 times, most recently
from
26a6959 to
b5d57e1
Compare
amlannandy
changed the base branch from
feat/infra-monitoring-k8s-nodes
to
feat/infra-monitoring-k8s
amlannandy
force-pushed
the
feat/infra-monitoring-k8s-clusters
branch
from
363d0e7 to
04a2a31
Compare
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
![ellipsis-dev[bot]](https://avatars.githubusercontent.com/in/64358?s=60&v=4){kind=small}
There was a problem hiding this comment.
❌ Changes requested. Reviewed everything up to 21a78f1 in 2 minutes and 3 seconds
More details
- Looked at
960lines of code in8files - Skipped
0files when reviewing. - Skipped posting
1drafted comments based on config settings.
1. frontend/src/container/InfraMonitoringK8s/Clusters/K8sClustersList.tsx:112
- Draft comment:
Avoid using inline styles in React components. Use external stylesheets, CSS classes, or styled components instead. This applies to other instances in the code as well. - Reason this comment was not posted:
Comment was not on a valid diff hunk.
Workflow ID: wflow_OWnIjk1DnyqVdvEW
Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.
amlannandy
force-pushed
the
feat/infra-monitoring-k8s-clusters
branch
from
21a78f1 to
a3a8f7c
Compare
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
There was a problem hiding this comment.
❌ Changes requested. Incremental review on a3a8f7c in 1 minute and 19 seconds
More details
- Looked at
922lines of code in5files - Skipped
0files when reviewing. - Skipped posting
3drafted comments based on config settings.
1. frontend/src/container/InfraMonitoringK8s/Clusters/utils.tsx:70
- Draft comment:
TheorderBycolumn 'cpu' does not exist in the data structure. Consider using a valid column name like 'cpuUsage'. - Reason this comment was not posted:
Comment was not on a valid diff hunk.
2. frontend/src/container/InfraMonitoringK8s/Clusters/utils.tsx:53
- Draft comment:
Consider defining a specific type forgroupedByMetainstead of usinganyto improve type safety. - Reason this comment was not posted:
Marked as duplicate.
3. frontend/src/container/InfraMonitoringK8s/Clusters/utils.tsx:58
- Draft comment:
Avoid using inline styles in React components. Instead, use external stylesheets, CSS classes, or styled components. - Reason this comment was not posted:
Marked as duplicate.
Workflow ID: wflow_Vuxm2IOGxRYpoF3F
Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
There was a problem hiding this comment.
👍 Looks good to me! Incremental review on 26a83fb in 1 minute and 11 seconds
More details
- Looked at
142lines of code in3files - Skipped
0files when reviewing. - Skipped posting
5drafted comments based on config settings.
1. frontend/src/container/InfraMonitoringK8s/Clusters/utils.tsx:1
- Draft comment:
The label for 'Memory Utilization' should be 'Memory Utilization (bytes)' instead of 'Memory Utilization (cores)'. - Reason this comment was not posted:
Marked as duplicate.
2. frontend/src/container/InfraMonitoringK8s/Clusters/utils.tsx:162
- Draft comment:
Ensure that the label for 'Memory Utilization' indefaultAddedColumnsmatches the actual data representation, which is in bytes. - Reason this comment was not posted:
Comment did not seem useful.
3. frontend/src/container/InfraMonitoringK8s/Clusters/utils.tsx:88
- Draft comment:
Avoid using inline styles for column headers. Use external stylesheets, CSS classes, or styled components instead. This issue is also present in other column definitions in this file. - Reason this comment was not posted:
Comment was on unchanged code.
4. frontend/src/container/InfraMonitoringK8s/Clusters/utils.tsx:104
- Draft comment:
Avoid using inline styles for column headers. Use external stylesheets, CSS classes, or styled components instead. This issue is also present in other column definitions in this file. - Reason this comment was not posted:
Marked as duplicate.
5. frontend/src/container/InfraMonitoringK8s/Clusters/utils.tsx:162
- Draft comment:
Avoid using inline styles for column headers. Use external stylesheets, CSS classes, or styled components instead. This issue is also present in other column definitions in this file. - Reason this comment was not posted:
Marked as duplicate.
Workflow ID: wflow_o6zABtnbfDdrAdq4
You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.
There was a problem hiding this comment.
👍 Looks good to me! Incremental review on f7f8712 in 14 seconds
More details
- Looked at
24lines of code in2files - Skipped
0files when reviewing. - Skipped posting
2drafted comments based on config settings.
1. frontend/src/hooks/infraMonitoring/useGetK8sClustersList.ts:41
- Draft comment:
The change fromGET_HOST_LISTtoGET_CLUSTER_LISTin the query key is correct and aligns with the new feature implementation. - Reason this comment was not posted:
Confidence changes required:0%
The change fromGET_HOST_LISTtoGET_CLUSTER_LISTin the query key is correct and aligns with the new feature implementation.
2. frontend/src/hooks/infraMonitoring/useGetK8sClustersList.ts:41
- Draft comment:
Avoid using inline styles in React components. Instead, use external stylesheets, CSS classes, or styled components. This comment applies to any other instances of inline styles in the codebase. - Reason this comment was not posted:
Confidence changes required:50%
The code is well-structured and follows the rules provided. The only issue is the use of inline styles, which is not present here. The code uses external constants and hooks appropriately.
Workflow ID: wflow_ayeWwrXLplRROnxa
You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
amlannandy
force-pushed
the
feat/infra-monitoring-k8s
branch
from
c89ffab to
79cae2d
Compare
YounixM
force-pushed
the
feat/infra-monitoring-k8s
branch
from
a294614 to
6855009
Compare
amlannandy
force-pushed
the
feat/infra-monitoring-k8s
branch
from
2edb730 to
579c7cb
Compare
YounixM
force-pushed
the
feat/infra-monitoring-k8s
branch
from
579c7cb to
22a33e3
Compare
amlannandy
force-pushed
the
feat/infra-monitoring-k8s-clusters
branch
from
f7f8712 to
92bd7d4
Compare
amlannandy
changed the title
There was a problem hiding this comment.
❌ Changes requested. Incremental review on 92bd7d4 in 1 minute and 46 seconds
More details
- Looked at
5524lines of code in33files - Skipped
0files when reviewing. - Skipped posting
6drafted comments based on config settings.
1. frontend/src/container/InfraMonitoringK8s/Clusters/ClusterDetails/Traces/ClusterTraces.styles.scss:53
- Draft comment:
Thefont-sizeandfont-weightproperties are defined twice in this rule. Consider removing the redundant definitions to improve clarity and maintainability. - Reason this comment was not posted:
Confidence changes required:50%
The code inClusterTraces.styles.scsshas a redundant CSS rule for.ant-table-thead > tr > th. Thefont-sizeandfont-weightare defined twice, which is unnecessary and could lead to confusion or maintenance issues.
2. frontend/src/container/InfraMonitoringK8s/Clusters/ClusterDetails/Traces/ClusterTraces.tsx:54
- Draft comment:
Theoffsetstate is initialized but never updated. If pagination is intended, ensure thatoffsetis updated appropriately to fetch the correct data. - Reason this comment was not posted:
Comment did not seem useful.
3. frontend/src/container/InfraMonitoringK8s/Clusters/ClusterDetails/Traces/ClusterTraces.tsx:138
- Draft comment:
ThetotalCountis calculated using the length of the list in the first result. Ensure this is accurate, especially if there are multiple results or pagination is involved. - Reason this comment was not posted:
Comment did not seem useful.
4. frontend/src/container/InfraMonitoringK8s/Clusters/K8sClustersList.tsx:65
- Draft comment:
The functionsetselectedClusterNameshould be renamed tosetSelectedClusterNameto follow camelCase naming conventions. - Reason this comment was not posted:
Confidence changes required:30%
InK8sClustersList.tsx, thesetselectedClusterNamefunction is used, but the naming convention is inconsistent with camelCase. It should besetSelectedClusterName.
5. frontend/src/container/InfraMonitoringK8s/Clusters/K8sClustersList.tsx:246
- Draft comment:
SettingorderBytonullwhen no sorter is provided might lead to unexpected behavior. Consider setting it to a default value instead. - Reason this comment was not posted:
Confidence changes required:40%
InK8sClustersList.tsx, thehandleTableChangefunction setsorderBytonullif no sorter is provided. This might lead to unexpected behavior if the default sorting is required.
6. frontend/src/container/InfraMonitoringK8s/Clusters/ClusterDetails/Traces/ClusterTraces.styles.scss:48
- Draft comment:
Use design tokens or predefined color constants instead of hardcoding color values for consistency. This is also applicable at line 108. - Reason this comment was not posted:
Marked as duplicate.
Workflow ID: wflow_ZFtoTWtTlGZss6xn
Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
1 similar comment
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
There was a problem hiding this comment.
👍 Looks good to me! Incremental review on 70e367b in 48 seconds
More details
- Looked at
31lines of code in2files - Skipped
0files when reviewing. - Skipped posting
3drafted comments based on config settings.
1. frontend/src/container/InfraMonitoringK8s/Clusters/K8sClustersList.tsx:292
- Draft comment:
Ensure that the change fromcluster_nametoclusterNameis consistent across the codebase for proper logging and data tracking. - Reason this comment was not posted:
Confidence changes required:50%
The logEvent function call was updated to use 'clusterName' instead of 'cluster_name'. This change should be consistent across the codebase to ensure proper logging and data tracking. The change seems correct as it aligns with the camelCase convention used in JavaScript.
2. frontend/src/container/InfraMonitoringK8s/Clusters/utils.tsx:151
- Draft comment:
The color value for the Tag component was changed to use a design tokenColor.BG_SLATE_400. Ensure this token is correctly defined and used consistently across the application. - Reason this comment was not posted:
Confidence changes required:50%
The color value for the Tag component was changed from a hardcoded hex value to a design tokenColor.BG_SLATE_400. This is a good practice as it promotes consistency and maintainability in the design system. Ensure that the design token is correctly defined and used across the application.
3. frontend/src/container/InfraMonitoringK8s/Clusters/utils.tsx:151
- Draft comment:
Avoid using inline styles in React components. Consider using external stylesheets, CSS classes, or styled components instead. This applies to other instances of inline styles in the code as well. - Reason this comment was not posted:
Comment was on unchanged code.
Workflow ID: wflow_RxfrSnsFZq6WNCfn
You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
There was a problem hiding this comment.
❌ Changes requested. Incremental review on f031c78 in 1 minute and 40 seconds
More details
- Looked at
399lines of code in6files - Skipped
0files when reviewing. - Skipped posting
4drafted comments based on config settings.
1. frontend/src/container/InfraMonitoringK8s/commonUtils.tsx:177
- Draft comment:
Remove console.log statements to avoid cluttering the console and potential performance issues in production. - Reason this comment was not posted:
Marked as duplicate.
2. frontend/src/container/InfraMonitoringK8s/commonUtils.tsx:198
- Draft comment:
Avoid usinganytype. Define specific types or interfaces for better type safety and maintainability. - Reason this comment was not posted:
Marked as duplicate.
3. frontend/src/container/InfraMonitoringK8s/Clusters/utils.tsx:87
- Draft comment:
Thesorterproperty is set tofalsefor columns where sorting is not needed. This is a good practice to avoid unnecessary sorting functionality. - Reason this comment was not posted:
Confidence changes required:20%
Thesorterproperty is set tofalsefor columns where sorting is not needed. This is a good practice to avoid unnecessary sorting functionality.
4. frontend/src/container/InfraMonitoringK8s/commonUtils.tsx:220
- Draft comment:
Avoid using inline styles for pagination in theMetricsTablecomponent. Consider using external stylesheets or styled components instead. - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable:
The comment appears to be incorrect. The code is using the proper antd Table API to configure pagination through props, not inline styles. The pagination={{ pageSize: 10, showSizeChanger: false }} syntax is the recommended way to configure Table pagination in antd. There are no actual CSS styles being applied inline here.
Could the comment author be referring to some other aspect of the pagination that I'm missing? Could there be a different best practice for antd Table pagination that I'm not aware of?
No - this is definitely using the standard antd Table API correctly. The pagination prop accepts an object for configuration, which is exactly what's being done here. There are no actual CSS styles involved.
The comment should be deleted as it incorrectly identifies proper antd Table prop usage as inline styling.
Workflow ID: wflow_zzH8XXUC5PuQyA0K
Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.
| type: 'tag', | ||
| isColumn: true, | ||
| }, | ||
| ]; |
| key: 'responseStatusCode-string-tag', | ||
| width: 145, | ||
| }, | ||
| ]; |
SagarRajput-7
requested changes
Jan 15, 2025
amlannandy
changed the base branch from
main
to
feat/infra-monitoring-k8s-namespaces
amlannandy
changed the base branch from
feat/infra-monitoring-k8s-namespaces
to
feat/infra-monitoring-k8s-deployments
amlannandy
force-pushed
the
feat/infra-monitoring-k8s-clusters
branch
from
f031c78 to
3a5a1b6
Compare
|
|
amlannandy
force-pushed
the
feat/infra-monitoring-k8s-deployments
branch
from
935f11d to
1d04816
Compare
amlannandy
changed the base branch from
feat/infra-monitoring-k8s-deployments
to
main
amlannandy
changed the base branch from
main
to
feat/infra-monitoring-k8s-deployments
amlannandy
force-pushed
the
feat/infra-monitoring-k8s-clusters
branch
from
3a5a1b6 to
3640874
Compare
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
There was a problem hiding this comment.
❌ Changes requested. Incremental review on 3640874 in 1 minute and 51 seconds
More details
- Looked at
332lines of code in6files - Skipped
0files when reviewing. - Skipped posting
7drafted comments based on config settings.
1. frontend/src/container/InfraMonitoringK8s/Clusters/ClusterDetails/Metrics/ClusterMetrics.tsx:84
- Draft comment:
Avoid usinganytype fordata. Define a specific type or interface for the expected structure ofdata. This applies to other instances ofanyin this file as well. - Reason this comment was not posted:
Marked as duplicate.
2. frontend/src/container/InfraMonitoringK8s/Clusters/ClusterDetails/Metrics/constants.ts:788
- Draft comment:
Avoid usinganytype fordata. Define a specific type or interface for the expected structure ofdata. This applies to other instances ofanyin this file as well. - Reason this comment was not posted:
Marked as duplicate.
3. frontend/src/container/InfraMonitoringK8s/Clusters/ClusterDetails/Metrics/constants.ts:1061
- Draft comment:
Avoid usinganytype fordata. Define a specific type or interface for the expected structure ofdata. This applies to other instances ofanyin this file as well. - Reason this comment was not posted:
Marked as duplicate.
4. frontend/src/container/InfraMonitoringK8s/Clusters/ClusterDetails/Metrics/constants.ts:1250
- Draft comment:
Avoid usinganytype fordata. Define a specific type or interface for the expected structure ofdata. This applies to other instances ofanyin this file as well. - Reason this comment was not posted:
Marked as duplicate.
5. frontend/src/container/InfraMonitoringK8s/Clusters/ClusterDetails/Metrics/constants.ts:1523
- Draft comment:
Avoid usinganytype fordata. Define a specific type or interface for the expected structure ofdata. This applies to other instances ofanyin this file as well. - Reason this comment was not posted:
Marked as duplicate.
6. frontend/src/container/InfraMonitoringK8s/commonUtils.tsx:7
- Draft comment:
Avoid using inline styles. Consider using CSS classes or styled components instead. - Reason this comment was not posted:
Comment was not on a valid diff hunk.
7. frontend/src/container/InfraMonitoringK8s/commonUtils.tsx:8
- Draft comment:
Avoid using inline styles. Consider using CSS classes or styled components instead. - Reason this comment was not posted:
Marked as duplicate.
Workflow ID: wflow_RpeFrxp4pvnCFOtq
Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.
| const chartData = useMemo( | ||
| () => | ||
| queries.map(({ data }) => { | ||
| const panelType = (data?.params as any)?.compositeQuery?.panelType; |
There was a problem hiding this comment.
Avoid using any type for data. Define a specific type or interface for the expected structure of data. This applies to other instances of any in this file as well.
amlannandy
force-pushed
the
feat/infra-monitoring-k8s-clusters
branch
from
3640874 to
e7e645e
Compare
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
There was a problem hiding this comment.
❌ Changes requested. Incremental review on e7e645e in 2 minutes and 30 seconds
More details
- Looked at
5525lines of code in32files - Skipped
0files when reviewing. - Skipped posting
8drafted comments based on config settings.
1. frontend/src/container/InfraMonitoringK8s/Clusters/ClusterDetails/Traces/ClusterTraces.styles.scss:45
- Draft comment:
Redundant CSS properties:font-sizeandfont-weightare defined twice in.ant-table-thead > tr > th. Consider removing the duplicates to clean up the code. - Reason this comment was not posted:
Confidence changes required:50%
The code inClusterTraces.styles.scsscontains a redundant CSS rule for.ant-table-thead > tr > thwherefont-sizeandfont-weightare defined twice. This redundancy should be removed to clean up the code.
2. frontend/src/container/InfraMonitoringK8s/Clusters/ClusterDetails/Traces/ClusterTraces.tsx:54
- Draft comment:
Theoffsetstate is initialized but never updated. If pagination is intended, consider implementing a mechanism to update theoffsetstate when pagination changes. - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable:
The code appears to intentionally use URL query parameters for pagination state rather than local state. The offset state seems to be a fallback value when paginationQueryData.offset is not available. The comment is technically correct that offset never changes, but this appears to be by design since pagination is handled through URL parameters instead.
I could be wrong about the intention - maybe this is actually a bug where the offset should be updated but isn't. The presence of the append logic in useEffect suggests pagination was intended.
The use of URL parameters for pagination state is a common pattern, and the code consistently uses paginationQueryData.offset || offset throughout. The append logic works with either source of offset.
The comment should be deleted since the offset behavior appears intentional, using URL parameters instead of local state for pagination.
3. frontend/src/container/InfraMonitoringK8s/Clusters/ClusterDetails/Traces/ClusterTraces.tsx:138
- Draft comment:
ThetotalCountis calculated using the length of the list in the first result. Consider summing the lengths of all lists in the results for accuracy. - Reason this comment was not posted:
Confidence changes required:50%
InClusterTraces.tsx, thetotalCountis calculated using the length of the list in the first result. This might not be accurate if there are multiple results. Consider summing the lengths of all lists in the results.
4. frontend/src/container/InfraMonitoringK8s/Clusters/K8sClustersList.tsx:65
- Draft comment:
The functionsetselectedClusterNameshould be renamed tosetSelectedClusterNameto follow camelCase naming conventions. - Reason this comment was not posted:
Confidence changes required:50%
InK8sClustersList.tsx, thesetselectedClusterNamefunction is used with a lowercase 's'. This is inconsistent with the camelCase naming convention and should be corrected tosetSelectedClusterName.
5. frontend/src/container/InfraMonitoringK8s/Clusters/K8sClustersList.tsx:286
- Draft comment:
Ensure thatrecord.keyis unique and correctly represents the cluster name when settingselectedClusterName. - Reason this comment was not posted:
Confidence changes required:50%
InK8sClustersList.tsx, thehandleRowClickfunction usesrecord.keyto setselectedClusterName. Ensure thatrecord.keyis unique and correctly represents the cluster name.
6. frontend/src/container/InfraMonitoringK8s/Clusters/K8sClustersList.tsx:313
- Draft comment:
Consider movingexpandedRowRenderoutside the component to avoid re-creation on each render, which can improve performance. - Reason this comment was not posted:
Confidence changes required:50%
InK8sClustersList.tsx, theexpandedRowRenderfunction is defined inside the component. Consider moving it outside to avoid re-creation on each render, which can improve performance.
7. frontend/src/container/InfraMonitoringK8s/Clusters/ClusterDetails/Traces/ClusterTraces.styles.scss:108
- Draft comment:
Use design tokens or predefined color constants instead of hardcoding color values likergba(255, 255, 255, 0.04)to maintain consistency in design and theming. - Reason this comment was not posted:
Marked as duplicate.
8. frontend/src/container/InfraMonitoringK8s/Clusters/ClusterDetails/Traces/ClusterTraces.styles.scss:189
- Draft comment:
Use design tokens or predefined color constants instead of hardcoding color values likergba(0, 0, 0, 0.04)to maintain consistency in design and theming. - Reason this comment was not posted:
Marked as duplicate.
Workflow ID: wflow_LH9YwEMpF3M2O2Ig
Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.
| font-size: 12px; | ||
| line-height: 18px; | ||
|
|
||
| background: rgba(171, 189, 255, 0.01); |
There was a problem hiding this comment.
Use design tokens or predefined color constants instead of hardcoding color values like rgba(171, 189, 255, 0.01) to maintain consistency in design and theming.
amlannandy
merged commit 65f2389
into
feat/infra-monitoring-k8s-deployments
7 of 8 checks passed
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
amlannandy
added a commit
that referenced
this pull request
Jan 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Implement the clusters entity in Infra Monitoring
Related Issues / PR's
Screenshots
Affected Areas and Manually Tested Areas
Infra Monitoring section
Important
Implement clusters entity in Kubernetes infrastructure monitoring with list and detail views, including metrics, logs, events, and traces.
K8sClustersList.tsx.ClusterDetails.tsx.getK8sClustersListAPI function ingetK8sClustersList.ts.useGetK8sClustersListhook inuseGetK8sClustersList.tsfor fetching cluster data.ClusterMetrics,ClusterLogs,ClusterEvents, andClusterTracescomponents for detailed cluster views..scssfiles.InfraMonitoringK8s.tsxto include clusters in the monitoring dashboard.This description was created by
for e7e645e. It will automatically update as commits are pushed.