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
Hello!
My test scenario implies interaction with https endpoint which relies on TLS SNI.
As far as I understand, yandex-tank generates config for phantom loader, and despite I specify hostname and port in load.yml it uses IP address for this configuration, so, phantom doesn't have an information about hostname => it can't provide ongoing secure connection with SNI field.
So, my endpoint can't determine destination of ingoing connection and just throws 503 and service doesn't exist error code.
My environment is openshift and traffic is going through openshift route to istio ingress gateway which terminates tls connection.
The text was updated successfully, but these errors were encountered:
Hello!
My test scenario implies interaction with https endpoint which relies on TLS SNI.
As far as I understand, yandex-tank generates config for phantom loader, and despite I specify hostname and port in load.yml it uses IP address for this configuration, so, phantom doesn't have an information about hostname => it can't provide ongoing secure connection with SNI field.
So, my endpoint can't determine destination of ingoing connection and just throws 503 and service doesn't exist error code.
My environment is openshift and traffic is going through openshift route to istio ingress gateway which terminates tls connection.
The text was updated successfully, but these errors were encountered: