Deploy a Kibana instance
editDeploy a Kibana instance
editTo deploy a simple Kibana specification, with one Kibana instance:
-
Specify a Kibana instance and associate it with your Elasticsearch
quickstart
cluster created previously under Deploying an Elasticsearch cluster:cat <<EOF | kubectl apply -f - apiVersion: kibana.k8s.elastic.co/v1 kind: Kibana metadata: name: quickstart spec: version: 8.16.0 count: 1 elasticsearchRef: name: quickstart EOF
-
Monitor Kibana health and creation progress.
Similar to Elasticsearch, you can retrieve details about Kibana instances with
get
:kubectl get kibana
And the associated Pods:
kubectl get pod --selector='kibana.k8s.elastic.co/name=quickstart'
Kibana will be status
available
onceget
reportsgreen
. If it experiences issues starting up, uselogs
against the pod in order to Troubleshoot Kibana start-up. -
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 known certificate authority and not trusted by your browser. You can temporarily acknowledge the warning for the purposes of this quick start but it is highly recommended that you configure valid certificates for any production deployments.Login as the
elastic
user. The password can be obtained with the following command:kubectl get secret quickstart-es-elastic-user -o=jsonpath='{.data.elastic}' | base64 --decode; echo
For a full description of each CustomResourceDefinition
(CRD), refer to the API Reference or view the CRD files in the project repository. You can also retrieve information about a CRD from the instance. For example, describe the Kibana CRD specification with describe
:
kubectl describe crd kibana
This completes the quickstart of deploying an Kibana instance on top of the ECK operator and deployed Elasticsearch cluster. We recommend continuing to updating your deployment. For more Kibana configuration options, refer to Running Kibana on ECK.