[oc] Agent cannot talk to collector

[ptescher]

Using latest operator on okd 4.4 beta5 the agent cannot talk back to the headless collector.

End up with lots of these in the agent:

{
    "level": "error",
    "ts": 1591844135.1634374,
    "caller": "grpc/reporter.go:74",
    "msg": "Could not send spans over gRPC",
    "error": "rpc error: code = Unavailable desc = last connection error: connection error: desc = \"transport: authentication handshake failed: read tcp 10.124.4.104:34158->10.125.4.13:14250: read: connection reset by peer\"",
    "stacktrace": "github.com/jaegertracing/jaeger/cmd/agent/app/reporter/grpc.(*Reporter).send\n\tgit.luolix.top/jaegertracing/jaeger/cmd/agent/app/reporter/grpc/reporter.go:74\ngit.luolix.top/jaegertracing/jaeger/cmd/agent/app/reporter/grpc.(*Reporter).EmitBatch\n\tgit.luolix.top/jaegertracing/jaeger/cmd/agent/app/reporter/grpc/reporter.go:53\ngit.luolix.top/jaegertracing/jaeger/cmd/agent/app/reporter.(*MetricsReporter).EmitBatch\n\tgit.luolix.top/jaegertracing/jaeger/cmd/agent/app/reporter/metrics.go:83\ngit.luolix.top/jaegertracing/jaeger/cmd/agent/app/reporter.(*ClientMetricsReporter).EmitBatch\n\tgit.luolix.top/jaegertracing/jaeger/cmd/agent/app/reporter/client_metrics.go:120\ngit.luolix.top/jaegertracing/jaeger/thrift-gen/jaeger.(*agentProcessorEmitBatch).Process\n\tgit.luolix.top/jaegertracing/jaeger/thrift-gen/jaeger/agent.go:138\ngit.luolix.top/jaegertracing/jaeger/thrift-gen/jaeger.(*AgentProcessor).Process\n\tgit.luolix.top/jaegertracing/jaeger/thrift-gen/jaeger/agent.go:112\ngit.luolix.top/jaegertracing/jaeger/cmd/agent/app/processors.(*ThriftProcessor).processBuffer\n\tgit.luolix.top/jaegertracing/jaeger/cmd/agent/app/processors/thrift_processor.go:121\ngit.luolix.top/jaegertracing/jaeger/cmd/agent/app/processors.NewThriftProcessor.func2\n\tgit.luolix.top/jaegertracing/jaeger/cmd/agent/app/processors/thrift_processor.go:86"
}

This appears to be cause by the fact that the headless service port name is grpc but should probably be tls-grpc when tls is enabled.

[ptescher]

Fixed by #1122

[jpkrohling]

@ptescher, thanks for reporting this issue! For some reason, it didn't appear in my radar, otherwise, we could have fixed it earlier.