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

Adjust Pods metadata, status #2910

Closed
11 of 12 tasks
akucharska opened this issue May 14, 2024 · 0 comments · Fixed by #2931
Closed
11 of 12 tasks

Adjust Pods metadata, status #2910

akucharska opened this issue May 14, 2024 · 0 comments · Fixed by #2931
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@akucharska
Copy link
Contributor

akucharska commented May 14, 2024

Description

Unify Pods metadata, status.

Acceptance Criteria

Metadata

  • Pod IP: (should be moved to status)

  • Status (should be moved to status)

Status

  • Host IP
  • Pod IP
  • podIPs ???
  • qosClass
  • conditions
  • containerStatuses
  • message /phase
  • ephemeralContainerStatuses (should be done when we add ephemeralContainer table
  • initContainerStatuses
  • nominatedNodeName

Overview card - nothing to show here
Events are OK
Resource Graph is OK

Reasons
A comprehensive review and enhancement of Busola's Views will ensure that users have all necessary information and tools at their fingertips, promoting efficiency and reducing the potential for errors.

Attachments

Useful Links
#2857
https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#pod-v1-core

@mrCherry97 mrCherry97 added the kind/feature Categorizes issue or PR as related to a new feature. label May 14, 2024
@akucharska akucharska self-assigned this May 15, 2024
@akucharska akucharska linked a pull request May 21, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants