You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 <resourceKind> --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 <resourceKind> --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
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Problem Statement
The dumped k8s resources and events (results of
kubectl get all
andkubectl 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 callingkubectl get <resourceKind> --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
kubectl get <resourceKind> --all-namespaces -o yaml
kubectl_get_all
kubectl describe all
Additional information
No response
Acceptance Criteria
kubectl get all
andkubectl describe all
are separated to a single file per resource kindThe text was updated successfully, but these errors were encountered: