Kong / Kong/kubernetes-testing-framework

Separate dumped k8s resources info by resource kind

Open
#634 0 comments 2 reactions 0 assignees View on GitHub
area/feature area/maintenance
Dominant language
Go
Stars
44
Forks
11
PR merge metrics
No merged PRs in 30d

Description

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Problem Statement

The dumped k8s resources and events (results of `kubectl get all` and `kubectl describe all`) are put into a single file. The file is usually very large and hard to find wanted object. Since the result is generated by calling `kubectl get --all-namespaces -o yaml` for each kind of resource, we could put the results into one file per resource kind to reduce the size of a single file and make each file clearer.

### Proposed Solution

- Output to a single file when we call `kubectl get --all-namespaces -o yaml`
- Name the file to the resource kind, and put the files to a directory `kubectl_get_all`
- Do the similar thing to `kubectl describe all`

### Additional information

_No response_

### Acceptance Criteria

- [ ] Results of `kubectl get all` and `kubectl describe all` are separated to a single file per resource kind

Contributor guide

Open the contributing guide

Research direction

Search the Go code for the kubectl get --all-namespaces -o yaml and kubectl describe all entry points, then trace how their output is assembled into a single file. Done means each resource kind has its own output file, with kubectl get results placed under kubectl_get_all, and the describe results separated similarly.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
devops, testing
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.