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

deployment and statefulesets require a namespcae #1386

Open
chris-sanders opened this issue Nov 1, 2023 · 0 comments
Open

deployment and statefulesets require a namespcae #1386

chris-sanders opened this issue Nov 1, 2023 · 0 comments

Comments

@chris-sanders
Copy link
Member

chris-sanders commented Nov 1, 2023

Bug Description

https://troubleshoot.sh/docs/analyze/deployment-status/#heading
The documentation states that namespace is optional and if provided limits the search to the specified namespace.
Testing today with a single deployment we found that the analyzer doesn't run when the deployment is in the non-default namespace and no analysis was generated. To get the analyzer to work we had to edit the spec and add the proper namespace in.

Expected Behavior

Documentation should be accurate. Namespace can be optional or not but should be documented as such.

Additional Context

Include the following information.

  • Troubleshoot version. I'm unsure was on a call with someone else I'll try to get that and edit this if I do.
    • Was the version available on krew the day this was posted should be latest
  • I am not sure at this time if the users kubeconfig had a context active with anything (like namespace) set. I will try to find out although that shouldn't cause the analyzer to act differently.
    • We believe there was a context and it matched the namespace where the deployment was
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant