troubleshoot
troubleshoot copied to clipboard
Preflight Checks and Support Bundles Framework for Kubernetes Applications
This is an attempt at solving a problem where we can't currently directly address resources collected by the cluster-resources collector. example bundle spec: ``` apiVersion: troubleshoot.sh/v1beta2 kind: SupportBundle metadata: name:...
**Describe the rationale for the suggested feature.** While trying to write a sample spec that looks for a particular image version of a component I expect to have installed, I...
**Describe the rationale for the suggested feature.** Currently the `clusterResources` collects logs from containers for pods that have terminated with an error or are crash-looping. There is a separate `logs`...
If Troubleshoot adds the clusterResources or ClusterInfo collector, ensure that this is added at the first element of the collectors array. Fixes: #767
### Problem to solve With the recently added feature to concatenate multiple specs together at runtime, we need to ensure that we are not unnecessarily running the `Cluster Resources` collectors...
Expanding the initial feature added in https://github.com/replicatedhq/troubleshoot/pull/709 to discover both support bundle and redactors specs across configmaps and secrets * Removes the `selector` flag which complimented the `load-cluster-specs` flag. It's...
### Problem to solve Perform quality gating checks on the developers machine before committing code into version control. ### Customer impact Potentially reduce bugs in the software by catching lint...
## Problem to solve The support bundle screen in KOTS looks very busy since the metadata/errors about pods failing was added. Furthermore, there are analyzers shown for pods that were...
testing.
# Design Proposal Available in [design folder](https://github.com/replicatedhq/troubleshoot/blob/main/design/proposal-updateable-specs.md) # Definition of done * [ ] Documentation updated to include how to enable feature and how it's useful * [ ] At...