# Custom kibana settings in ECK

**URL:** <https://discuss.elastic.co/t/custom-kibana-settings-in-eck/202006>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [October 2, 2019, 4:31pm UTC](https://discuss.elastic.co/t/custom-kibana-settings-in-eck/202006 "2019-10-02T16:31:26Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pebrc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pebrc/32/101790_2.png) [@pebrc](https://discuss.elastic.co/u/pebrc)\
**Post date:** [October 2, 2019, 7:57pm UTC](https://discuss.elastic.co/t/custom-kibana-settings-in-eck/202006/2 "2019-10-02T19:57:17Z")

</div>

Yes, you can combine both. We merge the settings you specify in the `config` section with the settings we derive from the `elasticsearchRef`

```auto
apiVersion: kibana.k8s.elastic.co/v1alpha1
kind: Kibana
metadata:
  name: kibana-sample
spec:
  version: 7.4.0
  nodeCount: 1
  config:
     elasticsearch.requestHeadersWhitelist:
     - authorization # or whatever you want here
  elasticsearchRef:
    name: "elasticsearch-sample"

```

In this example ECK takes care of the username, password, Elasticsearch URL and certificate authority setup but you can set a custom request header whitelist.

---

_[View the full topic](https://discuss.elastic.co/t/custom-kibana-settings-in-eck/202006)._