KHI v0.50.0 #416
kyasbal
announced in
Announcements
KHI v0.50.0
#416
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This release features a complete overhaul of the Kubernetes Audit Log parser. This significantly improves the visualization accuracy of resource state changes, specifically enabling more precise tracking of Pod behavior on Nodes and resource deletion flows. It also includes UX improvements for the New Inspection dialog.
🚀 Key Changes
Revamped Kubernetes Audit Log ParserThe Kubernetes Audit Log parsing logic has been completely rewritten, introducing the following enhancements:
bindwithpodpseudo-subresources under Node resourcesPreviously, KHI displayed
bindsubresources under Node resources to represent scheduling events. This has been replaced with newpodpseudo-subresources. This change allows you to view a detailed timeline directly from the Node's perspective, visualizing not just the scheduling timing, but also when a Pod became Running, when containers terminated, and if errors occurred.The logic for correlating Container IDs in
containerdlogs with Pods has been improved. In addition to the existing method using container startup logs, KHI now utilizes Container IDs found in thestatusfield of Pod resources within Audit Logs. This enables automatic and accurate correlation of container logs to Pods even if the specific container startup logs are outside the query range, provided the Audit Log contains the Container ID.metadata.uidin Control Plane logsKHI now generates a resource UID mapping during Audit Log parsing. This allows Control Plane logs that only contain
metadata.uid(without resource names) to be correctly mapped to the corresponding resource timeline.The visualization of
status.conditionsnow explicitly distinguishes between three states: "Unknown" (explicitly set to Unknown), "Condition does not exist", and "Insufficient log data to determine". This allows users to instantly determine whether the state is due to data loss or an actual Unknown state.KHI now recognizes
finalizersin the resource deletion process. When a DELETE request is issued, if finalizers are present, the resource is no longer treated as immediately "Deleted". Instead, it is displayed as "Terminating" until the finalizers are removed.UI/UX Improvements
The cluster name autocomplete behavior in the New Inspection dialog has been changed. The previous method of fetching the "current cluster list" via API has been removed. Instead, KHI now uses Cloud Monitoring labels to suggest only **clusters that actually existed during the input
End timeandDuration**. This ensures deleted clusters are suggested if they existed during the specified timeframe.🐛 Bug Fixes* Fixed subresource deletion tracking
Fixed an issue where subresources were not correctly recognized as deleted when their parent resource was deleted.
DeleteCollectionstate restorationFixed an issue where the manifest state was not correctly restored when multiple resources were bulk deleted via
DeleteCollectionAPI requests (e.g., during Namespace deletion).What's Changed
Features 🚀
Bug fix 🐛
Other Changes 🛠
Dependencies ⏫
Full Changelog: v0.49.1...v0.50.0
This discussion was created from the release KHI v0.50.0.
Beta Was this translation helpful? Give feedback.
All reactions