v0.2.2

v0.2.2

This is a bug fix release. As outline in #48 the previous version of Crash did not do a good job pulling all of the objects (specially logs) from the server. This fix attempts to bring KUBEGET on parity with kubectl cluster-info --dump.

KUBEGET objects

KUBEGET does the following when retrieving objects

• All retrieved objects are saved in its respective file placed in directory kubeget
• Each object retrieved is saved into a JSON file
• Namespaced objects are saved in a corresponding namespaced sub-directory
• Non-namespaced objects are saved in the root kubeget dir

The following shows an example directory layout of KUBEGET objects

crashd/stage
└── kubeget
    ├── apiservices.json
    ├── clusterinformations.json
    ├── clusterrolebindings.json
    ├── clusterroles.json
    ├── default
    │   ├── configmaps.json
    │   ├── controllerrevisions.json
    │   ├── cronjobs.json
    │   ├── daemonsets.json
    │   ├── deployments.json

KUBEGET logs

Fetching container logs with KUBEGET stores logs in a directory structure as follows

<namespace>/<pod-name>/<container-name>/container.log

Each container log is saved individually in its associated file as shown in the following example directory layout:

    ├── kube-system
    │   ├── calico-kube-controllers-ff95847f5-tjccn
    │   │   └── calico-kube-controllers
    │   │       └── calico-kube-controllers.log
    │   ├── calico-node-87b7l
    │   │   ├── calico-node
    │   │   │   └── calico-node.log
    │   │   ├── install-cni
    │   │   │   └── install-cni.log
    │   │   └── upgrade-ipam
    │   │       └── upgrade-ipam.log

Changelog

c558caa Merge pull request #52 from vladimirvivien/kubeget-logs-fix-take-2
fe86bb0 GitHub Actions CI update with [email protected]
a832e06 Documentation update for KUBEGET
9dcb1c8 Update KUBEGET to better organize object search results
c479bac Refactor k8s client code for object search