-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Support to bind TLS status as a part of component for service topology. #10522
Conversation
@kezhenxu94 One left issue caused by Service Mesh analysis. The TLS_MODE is not set by ALS analyzer, which leads to clientComponent is always |
We tried to check, the TLS property seems not to be reported from client side by ALS. |
This reverts commit 3876c6b.
TODO @kezhenxu94 @mrproliu We don't query source/target component IDs from CLI. We should fix these(I feel this may be caused by these fields being relatively new added). |
CHANGES
log.By this, the service topology(source/target components) includes the TLS for the service mesh case. The components could be [http, tls], [http, mtls], etc.
@toffentoffen Would you like to try this?