# Elastic client access using http in Kubernetes

**URL:** <https://discuss.elastic.co/t/elastic-client-access-using-http-in-kubernetes/196199>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security\
**Created:** [August 21, 2019, 10:18pm UTC](https://discuss.elastic.co/t/elastic-client-access-using-http-in-kubernetes/196199 "2019-08-21T22:18:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![frellus](https://avatars.discourse-cdn.com/v4/letter/f/5daacb/32.png) [@frellus](https://discuss.elastic.co/u/frellus)\
**Post date:** [August 21, 2019, 10:18pm UTC](https://discuss.elastic.co/t/elastic-client-access-using-http-in-kubernetes/196199/1 "2019-08-21T22:18:47Z")

</div>

We are experimenting with ECK (on-prem). LoadBalancer is not an option, we only have NodePort as a way to expose Elastic outside the cluster, or Ingress.

For Ingress, we terminate SSL at the ingress controller. Enabling SSL passthrough seems possible (enabling with the nginx --enable-ssl-passthrough flag), however this doesn't seem to be recommended.

We would rather turn off SSL for client traffic (yes, I know) and terminate at the ingress controller but can't see a way to do this. Is it even possible?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 18, 2019, 10:18pm UTC](https://discuss.elastic.co/t/elastic-client-access-using-http-in-kubernetes/196199/2 "2019-09-18T22:18:48Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.