You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 23, 2020. It is now read-only.
I have been testing flightpath for deployment and hit one major snag. A small number of our backend services talk https to the load-balancer and this appears to not be supported by flightpath.
The text was updated successfully, but these errors were encountered:
Can you specify if these services are connect enabled? Can you share the logs from Envoy process that is using Flightpath? A dump of the /config_dump admin endpoint would also be useful.
Right now flightpath configures tls only on connect enabled clusters. If these services are not connect enabled then that would require flightpath to know the details of the certificate to configure SAN, SNI and the CA trust chain. None of that is possible at the moment but can be added with little effort.
However, if the services are connect enabled then the problem is most likely between the service and the sidecar, not between Flightpath+Envoy and the sidecar.
I have been testing flightpath for deployment and hit one major snag. A small number of our backend services talk https to the load-balancer and this appears to not be supported by flightpath.
The text was updated successfully, but these errors were encountered: