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
Disabling TLS automatic configuration in Elasticsearch HTTP server to enable Linkerd to gather more statistics about connections. Linkerd is parsing plain text traffic (HTTP) and not encrypted (HTTPS)
Communications are still secured
Communications, within the cluster, between components will be still secured by linkerd-proxy running as sidecars of Elasticsearch and Fluent-Bit pods (automatic mTLS provided by Linkerd service mesh)
Communications, with components outside the cluster (i.e. ingestion of logs coming from control nodes like gateway), will be secured by Traefik acting as reverse proxy of Elasticsearch HTTP service, forcing TLS to the incoming communications (redirecting all HTTP traffic to HTTPS) and obtaining the corresponding TLS certificate from Cert-manager.
The text was updated successfully, but these errors were encountered:
Enhancement Request
gateway
), will be secured by Traefik acting as reverse proxy of Elasticsearch HTTP service, forcing TLS to the incoming communications (redirecting all HTTP traffic to HTTPS) and obtaining the corresponding TLS certificate from Cert-manager.The text was updated successfully, but these errors were encountered: