If you are using Amazon EKS, make sure the Kubernetes control plane is allowed to communicate with nodes port 443. This is required for communication with the Validating Webhook. For more information, see Recommended inbound traffic.

Similarly to Elasticsearch, you can retrieve details about Kibana instances:

kubectl get kibana

And the associated Pods:

kubectl get pod --selector='kibana.k8s.elastic.co/name=quickstart'

Access Kibana.

A ClusterIP Service is automatically created for Kibana:

kubectl get service quickstart-kb-http

Use kubectl port-forward to access Kibana from your local workstation:

kubectl port-forward service/quickstart-kb-http 5601

Open https://localhost:5601 in your browser. Your browser will show a warning because the self-signed certificate configured by default is not verified by a third party certificate authority and not trusted by your browser. You can either configure a valid certificate or acknowledge the warning for the purposes of this quick start.

Now that you have completed the quickstart, you can try out more features like tweaking persistent storage. The cluster that you deployed in this quickstart uses a default persistent volume claim of 1GiB, without a storage class set. This means that the default storage class defined in the Kubernetes cluster is the one that will be provisioned.

You can request a PersistentVolumeClaim with a larger size in the Elasticsearch specification or target any PersistentVolume class available in your Kubernetes cluster: