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

Print parent objects if a problem is found #33

Closed
thschue opened this issue Mar 23, 2023 · 0 comments · Fixed by #72
Closed

Print parent objects if a problem is found #33

thschue opened this issue Mar 23, 2023 · 0 comments · Fixed by #72
Assignees
Labels
good first issue Good for newcomers

Comments

@thschue
Copy link
Contributor

thschue commented Mar 23, 2023

Description

At the moment, only the affected resource is printed out, when a problem is found. As the configuration often has to be changed in a parent object, we should investigate the path to the root and print it out afterward.

Example

  • Troubleshooting Result: pod xyz is running out-of-memory
  • Normally, there is a Replicaset/Deployment managing this pod
  • Therefore, the path would be pod -> replicaset->deployment`
  • If we print this out, the end-user would get directed to the object which has to be changed
@thschue thschue added the good first issue Good for newcomers label Mar 23, 2023
@thschue thschue self-assigned this Mar 25, 2023
fyuan1316 pushed a commit to fyuan1316/k8sgpt that referenced this issue Jun 26, 2023
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant