Kibana

Kibana is the Elastic Stack analytics and visualization UI. The HelmForge chart connects Kibana to an existing Elasticsearch cluster or an optional HelmForge Elasticsearch dependency for self-contained environments.

Key Features

• Official Elastic Kibana image pinned to 9.4.2
• Optional Wolfi image flavor
• Basic auth or Elasticsearch service account token wiring
• Static encryption key support for HA sessions and encrypted saved objects
• Optional HelmForge Elasticsearch subchart for local and self-contained installs
• Ingress, Gateway API, dual-stack Services, NetworkPolicy, ServiceMonitor, PDB, and External Secrets

Installation

helm repo add helmforge https://repo.helmforge.dev
helm repo update
helm install kibana helmforge/kibana --namespace observability --create-namespace

helm install kibana oci://ghcr.io/helmforgedev/helm/kibana --namespace observability --create-namespace

Examples

Bundled Elasticsearch:

bundledElasticsearch:
  enabled: true

Secured Elasticsearch:

bundledElasticsearch:
  enabled: false

elasticsearch:
  hosts:
    - https://elasticsearch:9200
  auth:
    type: serviceAccountToken
    existingSecret: kibana-elasticsearch-token
  tls:
    enabled: true
    certificateAuthoritiesSecret: elasticsearch-ca

Operations

Set stable encryption keys before scaling beyond one replica. Elastic recommends matching Kibana and Elasticsearch versions across the stack.

Architecture

The chart deploys Kibana as the visualization layer for Elasticsearch. It can connect to an external Elasticsearch cluster or deploy the HelmForge Elasticsearch subchart for self-contained environments. Authentication can be disabled for local tests, use basic credentials, or use a service account token.

Runtime flow:

1. Users reach Kibana through Ingress or Gateway API.
2. Kibana reads stable encryption keys from generated or existing Secrets.
3. Kibana connects to one or more Elasticsearch endpoints.
4. Optional TLS CA material verifies Elasticsearch certificates.
5. Optional ServiceMonitor scrapes Kibana process metrics.

Production Values

Use stable encryption keys, TLS verification, service account tokens, and explicit network policy:

replicaCount: 2

bundledElasticsearch:
  enabled: false

elasticsearch:
  hosts:
    - https://elasticsearch:9200
  auth:
    type: serviceAccountToken
    existingSecret: kibana-elasticsearch-token
  tls:
    enabled: true
    certificateAuthoritiesSecret: elasticsearch-ca
    verificationMode: certificate

encryptionKeys:
  existingSecret: kibana-encryption-keys

networkPolicy:
  enabled: true

Stable encryption keys are required before scaling beyond one pod. Without them, sessions, saved object encryption, and reporting features can fail across restarts or replicas.

Bundled Elasticsearch

For development or self-contained validation, the HelmForge Elasticsearch dependency is enabled by default:

bundledElasticsearch:
  enabled: true

bundled-elasticsearch:
  clusterProfile: dev
  image:
    tag: '9.4.2'
  kibana:
    enabled: false
  master:
    persistence:
      enabled: false
  sysctlInit:
    enabled: false

For production, prefer a separately managed Elasticsearch release with its own capacity, backup, and upgrade plan.

Secrets And External Secrets

Service account token example:

elasticsearch:
  auth:
    type: serviceAccountToken
    existingSecret: kibana-elasticsearch-token

externalSecrets:
  enabled: true
  secretStoreRef:
    name: cluster-secrets
    kind: ClusterSecretStore
  data:
    - secretKey: service-account-token
      remoteRef:
        key: elastic/kibana
        property: service-account-token

Use the same target Secret names in Kibana values and ExternalSecret configuration to avoid race conditions or orphaned credentials.

Networking

Ingress example:

ingress:
  enabled: true
  ingressClassName: nginx
  hosts:
    - host: kibana.example.com
      paths:
        - path: /
          pathType: Prefix
  tls:
    - secretName: kibana-tls
      hosts:
        - kibana.example.com

Gateway API example:

gateway:
  enabled: true
  parentRefs:
    - name: shared-gateway
      namespace: gateway-system
  hostnames:
    - kibana.example.com

Upgrade Notes

Keep Kibana and Elasticsearch versions aligned. When upgrading:

1. Confirm Elasticsearch is compatible with the target Kibana version.
2. Back up saved objects and Elasticsearch data according to the Elastic runbook.
3. Keep encryption keys stable.
4. Roll out Kibana after Elasticsearch is healthy.

Validation

After deployment:

helm test kibana -n kibana
kubectl get pods -n kibana -l app.kubernetes.io/name=kibana
kubectl logs -n kibana deploy/kibana --since=10m
kubectl get events -n kibana --sort-by=.lastTimestamp

Also validate login, saved object access, index pattern discovery, and TLS verification against Elasticsearch.

Common Issues

Symptom	Likely Cause	Fix
Kibana reports encryption key warnings	Keys are generated or unstable	Set encryptionKeys.existingSecret.
Cannot connect to Elasticsearch	Wrong hosts, credentials, CA, or NetworkPolicy	Validate DNS, Secret keys, CA Secret, and egress.
TLS verification fails	CA Secret missing or verification mode wrong	Mount the correct CA and set verificationMode.
Version compatibility errors	Kibana and Elasticsearch versions differ	Align stack versions before rollout.

Values

Parameter	Default	Description
image.repository	docker.elastic.co/kibana/kibana	Official Kibana image.
image.flavor	default	Image flavor: default or wolfi.
replicaCount	1	Number of Kibana replicas.
elasticsearch.hosts	[http://elasticsearch:9200]	External Elasticsearch endpoints.
bundledElasticsearch.enabled	true	Deploy HelmForge Elasticsearch dependency.
elasticsearch.auth.type	none	Auth mode: none, basic, or serviceAccountToken.
encryptionKeys.existingSecret	""	Secret with stable Kibana encryption keys.
gateway.enabled	false	Render Gateway API HTTPRoute.
networkPolicy.extraEgress	[]	Additional NetworkPolicy egress rules.
serviceMonitor.enabled	false	Render ServiceMonitor.
externalSecrets.enabled	false	Render ExternalSecret resources.

Links

• Kibana
• Kibana GitHub
• Chart source