We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v0.0.3
No response
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
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
The text was updated successfully, but these errors were encountered:
There was a DNS resolution issue when I was building this, so we can probably alter it back, ill take a look
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Checklist
Affected Components
K8sGPT Version
v0.0.3
Kubernetes Version
No response
Host OS and its Version
No response
Steps to reproduce
kubectl logs deployment/k8sgpt-k8sgpt-operator-controller-manager
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
Actual behaviour
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: