Elasticsearch endpoint is throwing error (see below) when trying to reach the elasticearch endpoint through the istio virtual service. The enforcement of istio authpolicies, peerauths work that was done previously may require additional configuration changes for elasticsearch to work alongside the mtls istio-proxy.
upstream connect error or disconnect/reset before headers. retried and the latest reset reason: remote connection failure, transport failure reason: TLS_error:|268435581:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED:TLS_error_end:TLS_error_end
The error message we're seeing from the Istio proxy sidecar indicates a TLS (Transport Layer Security) handshake failure. Specifically, the error CERTIFICATE_VERIFY_FAILED suggests that the client (Istio proxy) was unable to verify the server's certificate during the TLS handshake.
with the mr to the elasticsearch package where elasticsearch certificates are handled by istio proxy envoy when istio is enabled, similar configuration for kibana needs to be enabled to allow traffic from elasticsearch to kibana, see issue represents this work: #207 (closed).
An issue was created to debug sso error as these changes in elasticsearch xpack.security settings conflicted with the sso secret xpack settings that get added to the config causing elasticsearch to fail at startup when sso is enabled. MR to rollback the 1.18.0-bb.3 changes until the sso error issue has been resolved.