Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

graphs with Waypoint proxy are not correctly generated #5539

Closed
Tracked by #5476
josunect opened this issue Oct 6, 2022 · 4 comments
Closed
Tracked by #5476

graphs with Waypoint proxy are not correctly generated #5539

josunect opened this issue Oct 6, 2022 · 4 comments
Labels
ambient Related to Istio Ambient Mesh research Any task that is not related to a change in the codebase sub-task Ties an issue to an epic

Comments

@josunect
Copy link
Contributor

josunect commented Oct 6, 2022

Traffic with istio sidecar (right) and waypoint proxy (left)

Screenshot from 2022-10-05 11-29-55

#5504 (comment)

@josunect josunect added enhancement This is the preferred way to describe new end-to-end features. research Any task that is not related to a change in the codebase sub-task Ties an issue to an epic and removed enhancement This is the preferred way to describe new end-to-end features. labels Oct 6, 2022
@jshaughn jshaughn added the ambient Related to Istio Ambient Mesh label Oct 6, 2022
@josunect
Copy link
Contributor Author

josunect commented Oct 7, 2022

With waypoint we have a couple of "issues":

  • It is attached to a SA.
  • There's no metrics for ratings, as the proxy created was associated to product application:
    image
    But, there are associated with the bookinfo with istio-sidecar
    image

Should we install a waypoint per application? Because even with the ztunnel metrics (tcp) we would be missing http metrics. L7 processing is not expected to run in the local node.

  • Also, the productPage traffic application is not related with the details or reviews apps (This may be "fixed" updating the query?)

@josunect
Copy link
Contributor Author

josunect commented Oct 17, 2022

Following this schema:

image

We will deploy a GW per App.

We will get all the L7 telemetry:

image

image

image

image

No traces or outbound metrics:

image

image

kubectl apply -f - <<EOF
apiVersion: gateway.networking.k8s.io/v1alpha2
kind: Gateway
metadata:
 name: productpage
 annotations:
   istio.io/service-account: bookinfo-reviews
spec:
 gatewayClassName: istio-mesh
 listeners:
 - name: default
   hostname: reviews
   port: 9080
   protocol: HTTP
   allowedRoutes:
     namespaces:
       from: All
EOF

kubectl apply -f - <<EOF
apiVersion: gateway.networking.k8s.io/v1alpha2
kind: Gateway
metadata:
 name: ratings
 annotations:
   istio.io/service-account: bookinfo-ratings
spec:
 gatewayClassName: istio-mesh
 listeners:
 - name: default
   hostname: ratings
   port: 9080
   protocol: HTTP
   allowedRoutes:
     namespaces:
       from: All
EOF

kubectl apply -f - <<EOF
apiVersion: gateway.networking.k8s.io/v1alpha2
kind: Gateway
metadata:
 name: details
 annotations:
   istio.io/service-account: bookinfo-details
spec:
 gatewayClassName: istio-mesh
 listeners:
 - name: default
   hostname: details
   port: 9080
   protocol: HTTP
   allowedRoutes:
     namespaces:
       from: All
EOF

image

@josunect
Copy link
Contributor Author

josunect commented Oct 18, 2022

  • It is possible to have 1 waypoint proxy for more than one application? - Istio Ambient will create one workload per service account:
    image
  • It is possible that the waypoint proxy is deployed in other namespace different that the application? Applying the wp proxy in other namespace doesn't create any metric.

@josunect
Copy link
Contributor Author

josunect commented Apr 3, 2023

Closed by: #5978

@josunect josunect closed this as completed Apr 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ambient Related to Istio Ambient Mesh research Any task that is not related to a change in the codebase sub-task Ties an issue to an epic
Projects
None yet
Development

No branches or pull requests

2 participants