[BUG]: old pod IP is used when k8sgpt-deployment pod is restarted

[jkleinlercher]

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

v0.0.3

Kubernetes Version

No response

Host OS and its Version

No response

Steps to reproduce

1. restart k8sgpt-deployment pod
2. look at operator logs:

kubectl logs deployment/k8sgpt-k8sgpt-operator-controller-manager

2023-05-31T20:03:39Z    ERROR   Reconciler error        {"controller": "k8sgpt", "controllerGroup": "core.k8sgpt.ai", "controllerKind": "K8sGPT", "K8sGPT": {"name":"k8sgpt-sample","namespace":"sx-k8sgpt"}, "namespace": "sx-k8sgpt", "name": "k8sgpt-sample", "reconcileID": "c5a51cb1-4a4b-49f8-af9f-db04e0e3f057", "error": "failed to call Analyze RPC: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp 10.130.3.224:8080: connect: no route to host\""}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler

Expected behaviour

the controller should be resilient against k8sgpt-deployment pod restarts. why do we use the pod IP in

k8sgpt-operator/controllers/k8sgpt_controller.go

Line 182 in 075caf5

address = fmt.Sprintf("%s:8080", podList.Items[0].Status.PodIP)

instead of the k8sgpt service?

Actual behaviour

No response

Additional Information

No response

[AlexsJones]

There was a DNS resolution issue when I was building this, so we can probably alter it back, ill take a look