# Proper way to remove external access from Kibana or Elasticsearch resource
**URL:** https://discuss.elastic.co/t/proper-way-to-remove-external-access-from-kibana-or-elasticsearch-resource/251283
**Category:** Elastic Cloud on Kubernetes (ECK)
**Created:** [October 7, 2020, 2:12pm UTC](https://discuss.elastic.co/t/proper-way-to-remove-external-access-from-kibana-or-elasticsearch-resource/251283 "2020-10-07T14:12:22Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@zvazquez](https://discuss.elastic.co/u/zvazquez)
#### Post date: [October 7, 2020, 2:12pm UTC](https://discuss.elastic.co/t/proper-way-to-remove-external-access-from-kibana-or-elasticsearch-resource/251283/1 "2020-10-07T14:12:22Z")
Hi,
We are in the process to enhance our Elasticsearch deployment within Kubernetes, we use the ECK tool to deploy elasticsearch and Kibana and in our original deployment we used the "http" tag to expose Elasticsearch and Kibana outside the cluster using LoadBalancer as follow:
```auto
http:
tls:
certificate:
secretName: es-cert
service:
spec:
type: LoadBalancer
```
Now we want to remove that access, since we will exposed both Elastic and Kibana behind a reverse proxy service in Kubernetes, to do not have dedicated load balancers for each.
What is the proper way to remove the load balancer, when we tried in sandbox by removing the "service" tag, it is not changing the Kubernetes service definition, and still has an external IP assigned.
Thanks in advance for your help,
Zareh
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 4, 2022, 8:14am UTC](https://discuss.elastic.co/t/proper-way-to-remove-external-access-from-kibana-or-elasticsearch-resource/251283/2 "2022-11-04T08:14:52Z")