troubleshoot
troubleshoot copied to clipboard
replicatedhq
Preflight Checks and Support Bundles Framework for Kubernetes Applications
**Describe the rationale for the suggested feature.** Sometimes a bundle may be destined only for internal use, or there may be concerns that useful data was removed by redactors. As...
Right now the output of troubleshoot project CLIs go to the users home directory, regardless of where they run the tool. This is confusing and should also be configurable. Thinking...
If a preflight check does not behave as expected, it can be hard to find the cause because the results of collectors are stored in memory and are discarded when...
log collectors should take a finite amount of time - say up to 1m by default - before exiting.
Like Deployment and StatefulSet Status, it would be useful to query Job Status. When running a migration job, this could be used to expose if it's failing or hasn't completed...
Currently, the only way to pass the URI to one of the database analyzers is to hard code it and write it into a spec. Often this is handled via...
The allocatable preflight checks seem useful to make sure that the cluster has enough resources we won't run into taints while installing the new application. However that only applies on...
Define CRD for Preflight and Support Bundle kinds such that they can be installed with an application, and then `kubectl support-bundle -n ` could detect the support bundle spec(s) defined...
Naming of collector output is unexpected, and doesn't match up well with what text analyzer expects. In particular https://troubleshoot.sh/reference/analyzers/regex/ is very wrong. What I've found digging through the source is...
Metadata
Owner
Metadata
Preflight Checks and Support Bundles Framework for Kubernetes Applications