Multiple TCP listener definitions for 0.0.0.0:6379 in Pilot (kubernetes external services) #365

Lookyan · 2018-05-30T05:33:07Z

Is this a BUG or FEATURE REQUEST?: BUG

What Version of Istio and Kubernetes are you using, where did you get Istio from, Installation details
Istio from 0.8 release branch built from source.

istioctl version
Version: 6dbbacac0b478017179480778637c9d8d781ac25-dirty
GitRevision: 6dbbacac0b478017179480778637c9d8d781ac25-dirty
User: lookyan
Hub: docker.io/istio
GolangVersion: go1.9.3
BuildStatus: Modified

kubectl version
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.0", GitCommit:"6e937839ac04a38cac63e6a7a306c5d035fe7b0a", GitTreeState:"clean", BuildDate:"2017-09-28T22:57:57Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.11", GitCommit:"1df6a8381669a6c753f79cb31ca2e3d57ee7c8a3", GitTreeState:"clean", BuildDate:"2018-04-05T17:16:46Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

Is Istio Auth enabled or not ?
I used istio.yaml with disabled Auth option.

What happened:
I have such messages in Pilot logs:

2018-05-29T14:48:49.006986Z	warn	Multiple TCP listener definitions for 0.0.0.0:6379 name:"tcp_0.0.0.0_6379" address:&lt;socket_address:&lt;address:"0.0.0.0" port_value:6379 &gt; &gt; filter_chains:&lt;filter_chain_match:&lt;&gt; filters:&lt;name:"envoy.tcp_proxy" config:&lt;fields:&lt;key:"deprecated_v1" value:&lt;bool_value:true &gt; &gt; fields:&lt;key:"value" value:&lt;struct_value:&lt;fields:&lt;key:"route_config" value:&lt;struct_value:&lt;fields:&lt;key:"routes" value:&lt;list_value:&lt;values:&lt;struct_value:&lt;fields:&lt;key:"cluster" value:&lt;string_value:"outbound|6379||external-app-redis00.default.svc.cluster.local" &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; fields:&lt;key:"stat_prefix" value:&lt;string_value:"outbound|tcp|6379" &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; deprecated_v1:&lt;bind_to_port:&lt;&gt; &gt;  external-autoload-redis01.default.svc.cluster.local
2018-05-29T14:48:49.007070Z	warn	Multiple TCP listener definitions for 0.0.0.0:6379 name:"tcp_0.0.0.0_6379" address:&lt;socket_address:&lt;address:"0.0.0.0" port_value:6379 &gt; &gt; filter_chains:&lt;filter_chain_match:&lt;&gt; filters:&lt;name:"envoy.tcp_proxy" config:&lt;fields:&lt;key:"deprecated_v1" value:&lt;bool_value:true &gt; &gt; fields:&lt;key:"value" value:&lt;struct_value:&lt;fields:&lt;key:"route_config" value:&lt;struct_value:&lt;fields:&lt;key:"routes" value:&lt;list_value:&lt;values:&lt;struct_value:&lt;fields:&lt;key:"cluster" value:&lt;string_value:"outbound|6379||external-app-redis00.default.svc.cluster.local" &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; fields:&lt;key:"stat_prefix" value:&lt;string_value:"outbound|tcp|6379" &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; deprecated_v1:&lt;bind_to_port:&lt;&gt; &gt;  external-autoload-redis02.default.svc.cluster.local
2018-05-29T14:48:49.007149Z	warn	Multiple TCP listener definitions for 0.0.0.0:6379 name:"tcp_0.0.0.0_6379" address:&lt;socket_address:&lt;address:"0.0.0.0" port_value:6379 &gt; &gt; filter_chains:&lt;filter_chain_match:&lt;&gt; filters:&lt;name:"envoy.tcp_proxy" config:&lt;fields:&lt;key:"deprecated_v1" value:&lt;bool_value:true &gt; &gt; fields:&lt;key:"value" value:&lt;struct_value:&lt;fields:&lt;key:"route_config" value:&lt;struct_value:&lt;fields:&lt;key:"routes" value:&lt;list_value:&lt;values:&lt;struct_value:&lt;fields:&lt;key:"cluster" value:&lt;string_value:"outbound|6379||external-app-redis00.default.svc.cluster.local" &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; fields:&lt;key:"stat_prefix" value:&lt;string_value:"outbound|tcp|6379" &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; deprecated_v1:&lt;bind_to_port:&lt;&gt; &gt;  external-avi-antifraud-redis01.default.svc.cluster.local

There are many entries like this in logs for each external service. And Pilot tries to reload them permanently and write it in logs.
Pilot uses 0.0.0.0 but these external services have different hosts and addr:port pair shouldn't be the same for them.

What you expected to happen:
Don't have these messages.

How to reproduce it:
Create several kubernetes external services with the same ports and run pilot.

The text was updated successfully, but these errors were encountered:

louiscryan added the area/networking label Jun 8, 2018

louiscryan added this to the 1.0 milestone Jun 13, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Multiple TCP listener definitions for 0.0.0.0:6379 in Pilot (kubernetes external services) #365

Multiple TCP listener definitions for 0.0.0.0:6379 in Pilot (kubernetes external services) #365

Lookyan commented May 30, 2018 •

edited

Loading

Multiple TCP listener definitions for 0.0.0.0:6379 in Pilot (kubernetes external services) #365

Multiple TCP listener definitions for 0.0.0.0:6379 in Pilot (kubernetes external services) #365

Comments

Lookyan commented May 30, 2018 • edited Loading

Lookyan commented May 30, 2018 •

edited

Loading