HTTP configuration

IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

HTTP configuration

Load balancer settings and TLS SANs

By default a ClusterIP Service is created and associated with the Kibana deployment. If you want to expose Kibana externally with a load balancer, it is recommended to include a custom DNS name or IP in the self-generated certificate.

apiVersion: kibana.k8s.elastic.co/v1
kind: Kibana
metadata:
  name: kibana-sample
spec:
  version: 8.19.8
  count: 1
  elasticsearchRef:
    name: "elasticsearch-sample"
  http:
    service:
      spec:
        type: LoadBalancer # default is ClusterIP
    tls:
      selfSignedCertificate:
        subjectAltNames:
        - ip: 1.2.3.4
        - dns: kibana.example.com

Provide your own certificate

edit

If you want to use your own certificate, the required configuration is identical to Elasticsearch. Check Custom HTTP certificate.

Disable TLS

edit

You can disable the generation of the self-signed certificate and hence disable TLS. This is not recommended outside of testing clusters.

apiVersion: kibana.k8s.elastic.co/v1
kind: Kibana
metadata:
  name: kibana-sample
spec:
  version: 8.19.8
  count: 1
  elasticsearchRef:
    name: "elasticsearch-sample"
  http:
    tls:
      selfSignedCertificate:
        disabled: true

« Secure settings Install Kibana plugins »