You are looking at preliminary documentation for a future release.
Not what you want? See the
current release documentation.
HTTP configurationedit
Load balancer settings and TLS SANsedit
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.13.0
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 certificateedit
If you want to use your own certificate, the required configuration is identical to Elasticsearch. Check Custom HTTP certificate.
Disable TLSedit
You can disable the generation of the self-signed certificate and hence disable TLS.
apiVersion: kibana.k8s.elastic.co/v1
kind: Kibana
metadata:
name: kibana-sample
spec:
version: 8.13.0
count: 1
elasticsearchRef:
name: "elasticsearch-sample"
http:
tls:
selfSignedCertificate:
disabled: true