Skip to content
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

EFK: Disable Elasticsearch server automatic TLS configuration #45

Closed
ricsanfre opened this issue Mar 22, 2022 · 0 comments · Fixed by #48
Closed

EFK: Disable Elasticsearch server automatic TLS configuration #45

ricsanfre opened this issue Mar 22, 2022 · 0 comments · Fixed by #48
Labels
enhancement New feature or request
Milestone

Comments

@ricsanfre
Copy link
Owner

Enhancement Request

  • 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.
@ricsanfre ricsanfre added the enhancement New feature or request label Mar 22, 2022
@ricsanfre ricsanfre changed the title EFK: Disable Elasticsearch automatic TLS EFK: Disable Elasticsearch server automatic TLS configuration Mar 22, 2022
@ricsanfre ricsanfre added this to the release 1.3 milestone Apr 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant