Closed wansuiye closed 6 years ago
mandarjog
commented
6 years ago This is working as expected. containerPorts are captured by the inbound ip tables rules and redirected thru the proxy. If the port is not captured, you will not see any metrics.
kyessenov
commented
6 years ago Isn't that counter intuitive? Should we do the opt out instead?
On Wed, Jun 6, 2018, 8:58 PM mandarjog notifications@github.com wrote:
This is working as expected. containerPorts are captured by the inbound ip tables rules and redirected thru the proxy. If the port is not captured, you will not see any metrics.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/istio/issues/issues/377#issuecomment-395285324, or mute the thread https://github.com/notifications/unsubscribe-auth/AJGIxi1y-fKfj9DnoC4-3FhpD38e7-mfks5t6KTsgaJpZM4UdsTL .
louiscryan
commented
6 years ago
Is this a BUG or FEATURE REQUEST?: yes
Did you review https://istio.io/help/ and existing issues to identify if this is already solved or being worked on?: yes
Bug: Y
What Version of Istio and Kubernetes are you using, where did you get Istio from, Installation details
Is Istio Auth enabled or not ? Did you install the stable istio.yaml, istio-auth.yaml.... or if using the Helm chart please provide full command line input. install 0.8.0, no auth no use helm
What happened: if deployment file not decare ports ，the proxy not report(telemetry) and check(policy)
What you expected to happen: the proxy can report to telemetry and check policy well，meanwhile can see request change in grafana
How to reproduce it: eg bookinfo's details-v1，if delete line 47~48 in bookinfo.yaml ,it will not work ,but in 0.7.1 it can work even if the deployment not decare ports
Feature Request: N
Describe the feature: