-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Milestone
Description
After deploying the latest conduit master and the emojivoto app to minikube, I'm unable to see any tap output when running conduit tap deploy emojivoto/voting-svc (from the Getting Started guide).
In the tap server logs, I see:
time="2018-01-11T02:01:59Z" level=info msg="Tapping 1 pods for target emojivoto/voting-svc"
time="2018-01-11T02:01:59Z" level=info msg="Establishing tap on 172.17.0.10:4190"
But the tap command does not produce any output.
In the voting service's proxy logs, I see:
1515635322.487561 INFO conduit_proxy using controller at HostAndPort { host: Domain("proxy-api.conduit.svc.cluster.local"), port: 8086 }
1515635322.487669 INFO conduit_proxy routing on V4(127.0.0.1:4140)
1515635322.487675 INFO conduit_proxy proxying on V4(0.0.0.0:4143) to None
1515635322.536696 INFO conduit_proxy::transport::connect "controller-client", DNS resolved proxy-api.conduit.svc.cluster.local to 10.107.64.120
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels