Replies: 1 comment 2 replies
-
@i-x and @alenkacz could probably help. Also we should fix docs after this |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been having issues connecting to RedPanda running in a local Kubernetes cluster both with Minikube (drivers:
docker
,hyperkit
,virtualbox
), and Docker-for-Desktop Kubernetes. I've only managed to get it working once, and that was with a Kubernetes cluster hosted on Google Cloud Platform.The tutorial I've been following has been: https://vectorized.io/docs/quick-start-kubernetes/
And the steps I take are:
kubectl get svc
:rpk --brokers 127.0.0.1:31595 topic list
I've tried the one-node-cluster many times but recently have just tried skipping straight to the external configuration, which is the one that worked on Google Cloud Platform.
Once everything is setup, when trying to list topics I get the following output:
With the main error being:
This error seems to only happen on my local setup, but does not occur when I set it up on Google Cloud Platform.
I am using the latest version of redpanda, kubernetes, docker, etc.
There's been a long discussion on Slack which may be helpful to reference: https://vectorizedcommunity.slack.com/archives/C01AJDUT88N/p1638358878411800
Some additional information:
$ kubectl get pod -o=wide
$ kubectl describe pod external-connectivity-0
$ kubectl describe pod external-connectivity-1
I noticed a few lines in the logs of
default-connectivity-0
where host is empty it seems:{host: , port: ...}
On my Google Cloud Engine logs, I printed the logs there and can verify there is no instance of
host: ,
which makes me extremely sure that this host being empty is the issue. If I can somehow make it0.0.0.0
instead of being empty, I'm sure it would fix it.Beta Was this translation helpful? Give feedback.
All reactions