Deploy Kibana (Deployment manifest)
Kibana is deployed with a small Deployment that creates one replica in theelastic-stack namespace and selects pods by the label app: kibana. The container exposes port 5601 — this is the port Kibana serves its web UI on.
ContainerCreating while the node pulls the Kibana image (the image is relatively large), then transition to Running:

Pods have internal IPs by design. To expose a pod so an external browser can reach it, you must create a Kubernetes Service (or use an Ingress / LoadBalancer). NodePort gives you a port on each node that forwards to the pod.
Expose Kibana with a NodePort Service
To let a browser outside the cluster reach Kibana, Bob exposes it with a Service of typeNodePort. The Service selects pods with app: kibana and maps the cluster port 5601 to a node port (for example, 30601). Any request to node:30601 on any node is forwarded to the pod port 5601.

PORT(S) column shows 5601:30601/TCP — the cluster port and the node port.
From any machine with network access to the cluster nodes, Bob can sanity-check Kibana with a simple HTTP request:
http://node01:30601/.
Create an index pattern and explore logs
When Bob opens Kibana and clicks Discover, Kibana asks which data (index) to view. It lists available indices (for examplefluentd-YYYY.MM.DD). Rather than repeatedly entering the date-stamped index name, Bob creates an index pattern using a wildcard like fluentd-* so the pattern matches current and future indices with that prefix.

@timestamp) and creates the index pattern. Kibana inspects the documents in the matched indices and displays discovered fields.
Back in Discover the interface populates: a time histogram shows log activity over the selected time range, and individual log lines appear below (newest first). These logs were generated by the application pod, collected by Fluentd on the node, stored in Elasticsearch, and are now visible in Kibana.
Example log lines:
USER1:
Caveat: Kibana depends on Elasticsearch. If Elasticsearch becomes resource-constrained (low memory, high load, or degraded cluster state), Kibana’s Discover view may not show errors — it may simply appear quiet or the histogram can flatten. Implement monitoring and alerting for Elasticsearch cluster health and node resources so the team is notified when the backend is unhealthy or searches stop returning expected results.
Links and references
- Kibana documentation: https://www.elastic.co/guide/en/kibana/current/index.html
- Elasticsearch: https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html
- Fluentd: https://www.fluentd.org/
- Kubernetes Services and NodePort: https://kubernetes.io/docs/concepts/services-networking/service/