Description
crust-gather is a great tool to collect state information on a Kubernetes cluster, to be later able to serve it offline. This eases troubleshooting of CI workflows on cloud-native apps.
Goals
- Hack on crust-gather. Possible paths to explore:
- Improve the release process (issue)
- Understand/document why not all generated cluster state archives contain an
apis.json
file, necessary to serve them - Fix
kubectl logs
output when filtering pods by label - Fix
kubectl get pods
output, which lists the name column twice
- Learn some Rust in the process
Resources
- crust-gather
- tour of Rust
- Curiosity!
Comments
-
7 days ago by tneau | Reply
Progress:
> Improve the release process (issue)
PR merged with added automation to bring consistency between the git tag and Cargo files, and documentation on the process.
> Understand/document why not all generated cluster state archives contain an apis.json file, necessary to serve them
Reproduced this locally, before realising that this was an issue with an outdated k3d version on my machine. Took the opportunity to install the latest version.
> Fix kubectl logs output when filtering pods by label
issue created and resolved through this.
> Fix kubectl get pods output, which lists the name column twice
issue created and resolved through this.
A new release is in the works for crust-gather, including these changes and of course using the new release workflow. It still needs a bit of debugging due to an unrelated issue (which might be fixed here).
Similar Projects
This project is one of its kind!