[Feature]: Enable "--input" flag for parsing k8s information from files instead of requiring k8s connection about k8sgpt

[Toerq]

Hi there! I'm interested in working on implementing the --input feature and was exploring the proposed solution.

While going through the discussion, I noticed the suggestion of using two commands:

1. k8sgpt analyze --save

2. k8sgpt analyze --from-save <file_path>

I was wondering if the k8sgpt analyze --save command is intended to capture the cluster state using a similar approach as the following command:

kubectl get all --all-namespaces -o yaml > cluster_state.yaml

I'm thinking of implementing the functionality by:

Using k8sgpt analyze --save to save the initial state.

Modifying k8sgpt analyze to accept the saved YAML file as input through the --from-save flag.

That would be a great start, but double check if there are any missing needed resources when running "get all". I don't think you will get any custom CRD resources that might be relevant for instance.

It would also be great if you can choose to mask any sensitive values such as "secrets" when running the "--save" command.

[AlexsJones]

It's a really interesting idea, but there would be a lot of "State" to download and capture locally.
It's possible, but we would need to really think about how we're doing that.
There might well be a few phases e.g.

Storing the initial data

1. k8sgpt analyze --save

Retrieving from files

2. k8sgpt analyze --from-save

[Toerq]

It's a really interesting idea, but there would be a lot of "State" to download and capture locally. It's possible, but we would need to really think about how we're doing that. There might well be a few phases e.g.

Storing the initial data

1. k8sgpt analyze --save

Retrieving from files

2. k8sgpt analyze --from-save

This would be an excellent solution.
Do you have any idea of how long this would take to implement?

[AlexsJones]

I don't think it's difficult technically, just a little time consuming, because you'd need to pull all of the resources that we have analysers for. Probably one of the easiest ways would be to extend the analyser interface to explain the types it needs to go get, then iterate through that and store locally into files.

I would say it's a few days of work

[the-tech-pilot]

Hi there! I'm interested in working on implementing the --input feature and was exploring the proposed solution.
While going through the discussion, I noticed the suggestion of using two commands:

1. k8sgpt analyze --save
2. k8sgpt analyze --from-save <file_path>

I was wondering if the k8sgpt analyze --save command is intended to capture the cluster state using a similar approach as the following command:
kubectl get all --all-namespaces -o yaml > cluster_state.yaml

I'm thinking of implementing the functionality by:

Using k8sgpt analyze --save to save the initial state.
Modifying k8sgpt analyze to accept the saved YAML file as input through the --from-save flag.

[ronaldpetty]

@the-tech-pilot how you doing on this? Anything you want to have peer reviewed or help with?

[harshanarayana]

@ronaldpetty @the-tech-pilot I have been working on getting something like this done for my internal use case and I got it working without too much of code changes using the client-go' fake client and prepend reactor.

harshanarayana@401ce5a

I would be more than happy to contribute a full working version of this if it is acceptable.

[harshanarayana]

Right now, In my case, the files are named as kubectl_get_<resource>_[--namespace_<ns>]_-o_yaml.log and a few lines at the tail end has metadata that I am stripping off.