NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #984 by repository stars
Latest stable
v0.61.1
Last release 9 days ago
13 Nov 2026
Ships on a steady schedule
a new release about every 2 weeks
Most releases are documented
notes for 45 of 51 stable releases
Nothing withdrawn
no release was ever pulled
2 years old
88 releases · first in 2025
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
feat(googlecloud): report missing IAM roles on permission errors and preserve client error types by @kyasbal in #1190
Full Changelog: v0.61.0...v0.61.1
<!-- Release notes generated using configuration in .github/release.yml at v0.61.1 -->
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.61.0...v0.61.1
Nothing published for this version
feat(mcp): add KHI Model Context Protocol server for agentic cluster investigation by @kyasbal in #1177
Full Changelog: v0.60.1...v0.61.0
<!-- Release notes generated using configuration in .github/release.yml at v0.61.0 -->
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.60.1...v0.61.0
Nothing published for this version
Nothing published for this version
Nothing published for this version
feat(k8snode): bind container and pod sandbox IDs in all node component logs by @kyasbal in #1028
Full Changelog: v0.59.0...v0.60.1
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
feat(k8sevent): replace resource UIDs with readable names in event summaries by @kyasbal in #973
Full Changelog: v0.58.4...v0.59.0
Nothing published for this version
Nothing published for this version
We've migrated the majority of the features from frontend heavy architecture to backend side. This enables us to gather logs even over 10M logs. In ad
We've migrated the majority of the features from frontend heavy architecture to backend side. This enables us to gather logs even over 10M logs.
In addition to this big architecture change, we've implemented full text search index in backend side. This allows us to search resources containing logs with specific keywords really faster. It would return the full text search query for 10M logs in few secounds!
Note I'll skip v0.58.0 and v0.58.1 for OSS release for some reasons. This v0.58.2 is our first release of v0.58.x.
Full Changelog: v0.58.0...v0.58.2
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
<!-- Release notes generated using configuration in .github/release.yml at v0.57.10 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.57.10 -->
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.57.9...v0.57.10
Full Changelog: v0.57.9...v0.57.10
<!-- Release notes generated using configuration in .github/release.yml at v0.57.9 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.57.9 -->
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.57.6...v0.57.9
Full Changelog: v0.57.6...v0.57.9
Nothing published for this version
Nothing published for this version
Nothing published for this version
<!-- Release notes generated using configuration in .github/release.yml at v0.57.6 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.57.6 -->
Note that v0.57.5 is abandoned due to our CD pipeline failure and tag immutability policy
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.57.4...v0.57.6
Note that v0.57.5 is abandoned due to our CD pipeline failure and tag immutability policy
Full Changelog: v0.57.4...v0.57.6
<!-- Release notes generated using configuration in .github/release.yml at v0.57.5 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.57.5 -->
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.57.4...v0.57.5
<!-- Release notes generated using configuration in .github/release.yml at v0.57.4 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.57.4 -->
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.57.3...v0.57.4
Full Changelog: v0.57.3...v0.57.4
<!-- Release notes generated using configuration in .github/release.yml at v0.57.3 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.57.3 -->
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.57.2...v0.57.3
Full Changelog: v0.57.2...v0.57.3
<!-- Release notes generated using configuration in .github/release.yml at v0.57.2 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.57.2 -->
This change includes organizing the top page README and minor frontend useful feature improvements.
Check our new KHI introductory video out!
https://github.com/user-attachments/assets/c868a8c2-b6a9-43dd-be12-ce1007c55559
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.57.1...v0.57.2
This change includes organizing the top page README and minor frontend useful feature improvements.
Check our new KHI introductory video out!
623308348-591357d0-9402-4dd1-b30f-6ae7e25b5cc9.mp4Full Changelog: v0.57.1...v0.57.2
Nothing published for this version
<!-- Release notes generated using configuration in .github/release.yml at v0.57.1 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.57.1 -->
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.57.0...v0.57.1
<!-- Release notes generated using configuration in .github/release.yml at v0.57.0 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.57.0 -->
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.56.7...v0.57.0
<!-- Release notes generated using configuration in .github/release.yml at v0.56.7 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.56.7 -->
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.56.6...v0.56.7
<!-- Release notes generated using configuration in .github/release.yml at v0.56.6 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.56.6 -->
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.56.5...v0.56.6
<!-- Release notes generated using configuration in .github/release.yml at v0.56.5 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.56.5 -->
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.56.4...v0.56.5
<!-- Release notes generated using configuration in .github/release.yml at v0.56.4 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.56.4 -->
Note: 0.56.3 is skipped for several reasons. Use 0.56.2 if you want to use a prior version.
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.56.2...v0.56.4
Nothing published for this version
<!-- Release notes generated using configuration in .github/release.yml at v0.56.2 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.56.2 -->
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.56.1...v0.56.2
<!-- Release notes generated using configuration in .github/release.yml at v0.56.1 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.56.1 -->
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.56.0...v0.56.1
<!-- Release notes generated using configuration in .github/release.yml at v0.56.0 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.56.0 -->
Previously .khi file format used JSON for storing its metadata and gzipped raw array buffer for long text part. This limits the maximum size of the logs due to the max string length accepted on V8.
This version changed .khi to use protocol buffer based file schema. It allows performant serialization/deserialization while we maintain file schema interface across backend and frontend.
Protocol buffer has limitation on the max size per single message, thus KHI concatenate multiple protos on simple KHI's container file format.
| scenario | log volume | old format size | new format size | reduction ratio |
|---|---|---|---|---|
| basic scenario | 223464 logs | 128.2MB | 19.4MB | x 6.6 |
| larger scenario | 1386843 logs | 885.3MB | 144.4MB | x6.1 |
This is not only for the file size issue. KHI needs decompress string data from the file at the beginning of the load to perform filtering and consume a lot of memory(The larger scenario data with old format couldn't be loaded on my environment.) This allows frontend to open larger log data.
Note that even if we support larger log volume, still it's recommended to set appropriate filter to query. Larger logs takes longer time to filter and the inspection experience would be worse.
KHI was initially designed only for visualizing Kubernetes logs. Thus timeline layer count was fixed and it always has the structure APIVersion -> Kind -> Namespace -> Resource -> SubResource.
However, now we have a lot of types of visualization are placed with hierarchical relationships such as .status.conditions or .metadata.ownerReference. We recently added support for CSM TD resources or Managed airflow. These were needed to be placed on timeline with mapping their concept to kubernetes concept forcibly.
New change allows defining new timeline type for each parsers and the count of layers of timeline hierarchy is not limited.
<img width="3840" height="1604" alt="image" src="https://github.com/user-attachments/assets/9467f0d3-d03b-4d80-96b6-1049318f68fd" />
With this change, Kubernetes resource hierarchy was changed to cluster name -> api version -> kind -> namespace -> resource -> subresource with aiming to support multi clusters.
<img width="3840" height="1604" alt="image" src="https://github.com/user-attachments/assets/45696670-8ab8-4501-9df7-c2f18bd367d3" />
By the change of timeline types, KHI no longer guarantee given data contains namespace or kind timeline. It needed more widely applicable filtering mechanism.
<img width="3840" height="1604" alt="image" src="https://github.com/user-attachments/assets/077593a7-0903-4ae4-a66c-761d79fc6469" />
<img width="3840" height="1604" alt="image" src="https://github.com/user-attachments/assets/0d19dea6-a533-4c01-992d-af39b320b562" />
The new filtering system is based on CEL based highly flexible filtering system. Now advanced user can input the filter directly. One of the example of this usage is to filter timelines by its manifest property.
The screenshot captures filtering timelines which has status.qosClass = Burstable. This allows us to find resources with more complex conditions.
<img width="3840" height="1604" alt="image" src="https://github.com/user-attachments/assets/2b3afed9-3f2a-4684-ae3c-4f3a21865384" />
KHI hasn't supported severity based filtering. This was not from the architectural limit, but more like my own ideological policy. But now I supported it as there were many requests on it. But note that severities in distributed system sometimes become misleading because each component decides its severity from its own perspective. Severity is not a universal criteria of logs.
<img width="890" height="904" alt="image" src="https://github.com/user-attachments/assets/486d322e-a1c5-4925-bbfa-fb4faa7d0199" /> <img width="628" height="740" alt="image" src="https://github.com/user-attachments/assets/a695918c-64fc-440d-a2ef-ed2d134086b2" />
Our log or diff components hasn't provided searching capability. It lead user to use in-browser search but it sometimes hit other elements not on the logs or the manifest.
https://github.com/user-attachments/assets/c05fc8ee-780a-4d47-b74d-3e581c98b994
Now KHI's graph view is integrated on the dockable window. It allows us to see the diagram along with the timeline.
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.55.2...v0.56.0
Nothing published for this version
Nothing published for this version
<!-- Release notes generated using configuration in .github/release.yml at v0.55.2 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.55.2 -->
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.55.1...v0.55.2
Nothing published for this version
<!-- Release notes generated using configuration in .github/release.yml at v0.55.1 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.55.1 -->
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.55.0...v0.55.1
<!-- Release notes generated using configuration in .github/release.yml at v0.55.0 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.55.0 -->
We've updated the behavior of sticky header in timeline view. That used to show kind and namespace timeline only, but now it can show resource timeline as well from this version. This helps us understand timeline of a resource that has a lot of subresources.
Old behavior
https://github.com/user-attachments/assets/d6d46134-6874-45b8-8677-2dccdbc786d2
New implementation
https://github.com/user-attachments/assets/e0c65839-a294-4243-b8fd-6657b1f943e4
This is a part of refactoring that aim to replace the KHI file format in future. This sticky header behavior will be even better after the big change soon later...
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.54.0...v0.55.0
Nothing published for this version
<!-- Release notes generated using configuration in .github/release.yml at v0.54.0 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.54.0 -->
KHI v0.54.0 includes new support for the audit log of TD resource modifications related to CSM.
If you run CSM with TD based control plane, resources like HttpRoute, BackendConfig or NEGs will be configured in the response to CSM resource changes on clusters. KHI now effectively visualizes modifications for these TD based resources.
Try this feature with enabling CSM Resource Audit Logs after selecting in the cluster type.
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.53.0...v0.54.0
fix(web): resolve Dart Sass deprecation warnings in timeline-frame by @kyasbal in https://github.com/GoogleCloudPlatform/khi/pull/588
<!-- Release notes generated using configuration in .github/release.yml at v0.53.0 -->
Docking Windows
KHI now uses docking window on its layout. It enables you to work with massive logs with limited screen area. <img width="3840" height="1926" alt="image" src="https://github.com/user-attachments/assets/c29c6f99-4059-4a70-9284-1203fffd22bf" /> <img width="3840" height="1926" alt="image" src="https://github.com/user-attachments/assets/da493d6c-eeb0-4d74-a0ea-f54dd6ffa079" />
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.52.12...v0.53.0
<!-- Release notes generated using configuration in .github/release.yml at v0.52.12 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.52.12 -->
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.52.11...v0.52.12
<!-- Release notes generated using configuration in .github/release.yml at v0.52.11 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.52.11 -->
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.52.10...v0.52.11
<!-- Release notes generated using configuration in .github/release.yml at v0.52.10 -->
<!-- Release notes generated using configuration in .github/release.yml at v0.52.10 -->
Full Changelog: https://github.com/GoogleCloudPlatform/khi/compare/v0.52.9...v0.52.10
Nothing published for this version
One column per month.