"Cannot connect to: redis" happened on k3s deployment

kumahq / kuma-counter-demo

This is the counter demo for Kuma, that demonstrates the capabilities of the service mesh.

Apache License 2.0

15 stars 16 forks source link

Closed neilbowman666 closed 1 year ago

neilbowman666 commented 1 year ago

Same error occured when I deployed this demo app with kuma-cp installed or not.

container: k3s

k3s default CNI: VXLAN

UI shows followed pic:

And the logs followed:

neilbowman666 commented 1 year ago

When I deploy this project rawly on my host machine, redis connecting OK.

jakubdyszkiewicz commented 1 year ago

Triage: if you can see it without sidecars, this seems to be a problem with the env instead. We use k3d (k3s in docker) in e2e tests and it is ok.