[Bug]: --kubeconfig doesn't work

[jianzhangbjz]

Checklist

• I've searched for similar issues and couldn't find anything matching
• I've included steps to reproduce the behavior

Affected Components

• K8sGPT (CLI)
• K8sGPT Operator

K8sGPT Version

k8sgpt: 0.3.7 (1bc0f42), built at: unknown

Kubernetes Version

v1.27.0

Host OS and its Version

No response

Steps to reproduce

1. In a cluster
2. export another KUBECONFIG
3. Run the k8sgpt --kubeconfig=/tmp/kubeconfig-3608642416 analyze -aed

Expected behaviour

It should use the KUBECONFIG when users export it.

Actual behaviour

The cluster we export.

$ oc config get-contexts
CURRENT   NAME    CLUSTER                AUTHINFO   NAMESPACE
*         admin   ci-op-1fym1gz3-564bf   admin  
$ oc whoami
system:admin

But, it still read the InClusterConfig config, not the specific KUBECONFIG

k8sgpt --kubeconfig=/tmp/kubeconfig-3608642416 analyze -aed
AI Provider: openai

Warnings : 
- [MutatingWebhookAnalyzer] mutatingwebhookconfigurations.admissionregistration.k8s.io is forbidden: User "system:serviceaccount:ci-op-1fym1gz3:aws-ipi-ovn-efs-fips-f14" cannot list resource "mutatingwebhookconfigurations" in API group "admissionregistration.k8s.io" at the cluster scope
- [NodeAnalyzer] nodes is forbidden: User "system:serviceaccount:ci-op-1fym1gz3:aws-ipi-ovn-efs-fips-f14" cannot list resource "nodes" in API group "" at the cluster scope
- [StatefulSetAnalyzer] statefulsets.apps is forbidden: User "system:serviceaccount:ci-op-1fym1gz3:aws-ipi-ovn-efs-fips-f14" cannot list resource "statefulsets" in API group "apps" at the cluster scope
- [ValidatingWebhookAnalyzer] validatingwebhookconfigurations.admissionregistration.k8s.io is forbidden: User "system:serviceaccount:ci-op-1fym1gz3:aws-ipi-ovn-efs-fips-f14" cannot list resource "validatingwebhookconfigurations" in API group "admissionregistration.k8s.io" at the cluster scope
- [PodAnalyzer] pods is forbidden: User "system:serviceaccount:ci-op-1fym1gz3:aws-ipi-ovn-efs-fips-f14" cannot list resource "pods" in API group "" at the cluster scope
- [IngressAnalyzer] ingresses.networking.k8s.io is forbidden: User "system:serviceaccount:ci-op-1fym1gz3:aws-ipi-ovn-efs-fips-f14" cannot list resource "ingresses" in API group "networking.k8s.io" at the cluster scope
- [PvcAnalyzer] persistentvolumeclaims is forbidden: User "system:serviceaccount:ci-op-1fym1gz3:aws-ipi-ovn-efs-fips-f14" cannot list resource "persistentvolumeclaims" in API group "" at the cluster scope
- [CronJobAnalyzer] cronjobs.batch is forbidden: User "system:serviceaccount:ci-op-1fym1gz3:aws-ipi-ovn-efs-fips-f14" cannot list resource "cronjobs" in API group "batch" at the cluster scope
- [ServiceAnalyzer] endpoints is forbidden: User "system:serviceaccount:ci-op-1fym1gz3:aws-ipi-ovn-efs-fips-f14" cannot list resource "endpoints" in API group "" at the cluster scope
- [ReplicaSetAnalyzer] replicasets.apps is forbidden: User "system:serviceaccount:ci-op-1fym1gz3:aws-ipi-ovn-efs-fips-f14" cannot list resource "replicasets" in API group "apps" at the cluster scope
- [DeploymentAnalyzer] deployments.apps is forbidden: User "system:serviceaccount:ci-op-1fym1gz3:aws-ipi-ovn-efs-fips-f14" cannot list resource "deployments" in API group "apps" at the cluster scope

No problems detected

Additional Information

No response

[jianzhangbjz]

/kind bug

[arbreezy]

@jianzhangbjz , I tried to reproduce.

From my tests when you specify --kubeconfig or/and --context is working fine.

I realized that you want to connect from within a cluster to an external one and yes this is not doable atm.