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

[Toerq]

Checklist

• I've searched for similar issues and couldn't find anything matching
• I've discussed this feature request in the K8sGPT Slack and got positive feedback

Is this feature request related to a problem?

None

Problem Description

Currently, the k8sgpt tool requires direct access to a kubeconfig and network access to the Kubernetes cluster to perform the scanning. This requirement creates some limitations, especially in environments with strict security policies or limited network connectivity.

This requirement, in combination with the need for a network connection to an instance running localAI further limits the flexibility.

This limitation makes it challenging to use the tool in isolated, on-prem solutions with limited internet access, or highly secure environments where such access is restricted or not feasible.

Solution Description

Introduce an --input flag for the gpt4all command that allows users to directly provide YAML files as input. These input files should be generated by running e.g. "kubectl get nodes -o yaml" or whatever input format k8sgpt can parse.

This feature would enable comprehensive scanning and analysis without the need for direct access to a kubeconfig or live connection to a Kubernetes cluster.

Additionally, also expand the documentation to inform the users what (e.g. kubectl) commands would need to be run to generate these files.

Benefits

Enables the use of k8sgpt in secure, isolated, or air-gapped environments by removing the direct dependency on kubeconfig and live cluster access.
Expands the tool's usability by facilitating offline analysis and testing against pre-generated data.

Potential Drawbacks

No response

Additional Information

No response

[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.

[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.

[ronaldpetty]

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