istio: VM service TCP missing destination.service - mixer/pilot service uid/pods match

Currently any inbound call to a TCP service on VM yields the following error in mixer:

E1017 05:58:02.900969       1 grpcServer.go:181] Check returned with
error : INTERNAL (destination.service identity not found in
attributes[context.time destination.ip source.ip destination.uid
context.protocol source.port])

We may want to solve this globally where mixer would stop using pods for figuring out service names

ideally a (quick) fix would be cherry picked in 0.2 (a hacky version of that is https://github.com/istio/pilot/pull/1515)

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 16 (16 by maintainers)

Commits related to this issue

Automator: update common-files@master in istio/api@master (#1302) — committed to thedemodrive/istio by istio-testing 4 years ago

Most upvoted comments

https://github.com/istio/istio/pull/1845 added destination.service to TCP config filter attribute list (see mixerTCPConfig).

https://github.com/istio/mixerclient/pull/248 includes these attributes in Report/Check calls to mixer (see https://github.com/istio/mixerclient/pull/248/files#diff-095c85dbca675290424501565e6f8e20R37), though this support may have also been present in earlier versions of mixerclient. cc @qiwzhang

ayj on Jan 2, 2018