DEV.co
Open-Source Observability · kiali

kiali

Kiali is a web-based management console for Istio service meshes that provides real-time observability, traffic visualization, and operational insights. It runs as an Istio add-on and helps operators understand and troubleshoot service-to-service communication in Kubernetes clusters.

Source: GitHub — github.com/kiali/kiali
3.6k
GitHub stars
561
Forks
Go
Primary language
Apache-2.0
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositorykiali/kiali
Ownerkiali
Primary languageGo
LicenseApache-2.0 — OSI-approved
Stars3.6k
Forks561
Open issues122
Latest releasev2.28.0 (2026-06-22)
Last updated2026-07-08
Sourcehttps://github.com/kiali/kiali

What kiali is

Written in Go (backend) and Node.js/React (frontend), Kiali integrates with Istio control plane APIs to visualize mesh topology, monitor traffic metrics, and validate service mesh configurations. It reads Istio resources from Kubernetes and provides both REST APIs and a UI for mesh management.

Quickstart

Get the kiali source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/kiali/kiali.gitcd kiali# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Multi-service traffic visibility in Istio

Visualize request flows, latencies, and error rates across services without application instrumentation. Essential for debugging cross-service issues and understanding runtime behavior of microservices.

Istio configuration validation and troubleshooting

Inspect VirtualServices, DestinationRules, and other mesh resources; identify misconfigurations that cause traffic failures. Kiali surfaces warnings about invalid or incomplete configurations.

Distributed tracing and observability integration

Correlate traffic visualization with traces from Jaeger/Zipkin and metrics from Prometheus. Provides a unified pane of glass for understanding request paths and performance bottlenecks.

Implementation considerations

  • Requires Go (specified minimum version in Makefile), Node.js >= 20, Docker/Podman, git, gcc, and GNU make for local builds; production deployments use Helm charts and Kubernetes operators.
  • Backend and frontend are built and deployed separately; frontend assets must be embedded in backend binary, requiring coordinated builds.
  • Multi-cluster support requires kubeconfig configuration and cluster name overrides for contexts that do not match Istio cluster names.
  • Hot-reload development mode supported via air for backend; frontend dev server available for local iteration.
  • Operator-based deployment recommended for production; manual KialCR creation required to configure and deploy Kiali instances.

When to avoid it — and what to weigh

  • Not using Istio service mesh — Kiali is purpose-built for Istio and has no utility in non-Istio environments. Requires an existing Istio installation and compatible Kubernetes cluster.
  • Seeking a standalone APM or metrics platform — Kiali is a management UI for mesh-specific operations, not a general application performance monitoring tool. It depends on Prometheus, Jaeger, and Istio for underlying data.
  • Operating in air-gapped or highly restricted networks — Deployment requires container images, external dependencies (Prometheus, Jaeger, Istio), and internet access for documentation and community support integration.
  • Minimal Kubernetes footprint required — Kiali adds pods, RBAC rules, and network policies to the cluster. Suitable only where observability overhead is acceptable and resources are available.

License & commercial use

Licensed under Apache License 2.0 (Apache-2.0). This is a permissive OSI-approved license allowing commercial use, modification, and distribution with attribution and license reproduction requirements.

Apache-2.0 permit use in closed-source and commercial products, subject to license and copyright notice inclusion. No commercial restrictions detected in license text; however, always include LICENSE file and NOTICE of changes in distributions. Review any proprietary dependencies (frontend tooling, etc.) for additional restrictions.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationAdequate
License clarityClear
Deployment complexityHigh
DEV.co fitStrong
Assessment confidenceHigh
Security considerations

Kiali gains RBAC access to Istio and Kubernetes APIs; runs as cluster component with elevated privileges. Typical considerations: (1) restrict RBAC to least-privilege role binding, (2) validate all upstream dependencies (Istio, Prometheus, Jaeger) for vulnerabilities, (3) review any OIDC/OpenID integration for authentication bypass risks, (4) isolate network access to Kiali UI and APIs. No known exploit details available from provided data.

Alternatives to consider

Grafana + Prometheus + Istio datasources

Provides metrics and dashboarding but lacks Istio-native topology visualization and configuration validation; requires manual dashboard curation.

Envoy admin UI (via port-forward)

Lower overhead, direct sidecar introspection; but limited scope and requires per-pod access; no unified mesh view.

Datadog, New Relic, Lightstep APM agents

Commercial observability platforms with broader application instrumentation; more expensive, not specific to Istio mesh management.

Software development agency

Build on kiali with DEV.co software developers

Review the full documentation, test multi-cluster setup, and assess integration with your Prometheus and Jaeger stacks. Start with the run-integration-tests.sh script for a quick local demo.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

kiali FAQ

Does Kiali work without Prometheus and Jaeger?
Kiali can display service mesh topology and configuration from Istio APIs alone. Metrics (latency, error rate, request volume) and distributed traces require Prometheus and Jaeger/Zipkin respectively. Basic observability works without them; full observability requires integration.
Can Kiali manage multi-cluster Istio meshes?
Yes, via kubeconfig context configuration. Multiple clusters can be specified with `--remote-cluster-contexts` and `--cluster-name-overrides` flags. Requires proper networking and Istio federation setup between clusters.
What is the resource overhead of deploying Kiali?
Not specified in provided data. Deployment adds pods (server, operator) and RBAC policies to the cluster. Exact resource requests/limits require reviewing Helm values and operator deployment specs; typical for observability sidecars, but varies by scale.
Is the AI documentation feature production-ready?
No. README explicitly marks AI integration as developer preview with evolving APIs and configuration that may change without notice. Not recommended for production workflows.

Software development & web development with DEV.co

DEV.co helps companies turn open-source tools like kiali into production software. Our software development services cover the full lifecycle — architecture, web development, integration, and maintenance — delivered by software developers and web developers who ship. Engage our software development agency to implement or customize it for your open-source observability stack.

Evaluate Kiali for Your Istio Deployment

Review the full documentation, test multi-cluster setup, and assess integration with your Prometheus and Jaeger stacks. Start with the run-integration-tests.sh script for a quick local demo.