Conversation
format_health_lines now prefers health.headline when the API provides one,
showing the customer-friendly label (e.g. "Out of memory") instead of the
raw k8s vocabulary ("CrashLoopBackOff (OOMKilled, exit 137)"). The exit
code is appended as its own subhead segment so it remains visible.
Older API responses without the headline field continue to render via the
existing string-construction path — additive on the API side, so no
release-order constraint between API and CLI.
cbrianhill
approved these changes
May 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
format_health_lines now prefers health.headline when the API provides one, showing the customer-friendly label (e.g. "Out of memory") instead of the raw k8s vocabulary ("CrashLoopBackOff (OOMKilled, exit 137)"). The exit code is appended as its own subhead segment so it remains visible.
Older API responses without the headline field continue to render via the existing string-construction path — additive on the API side, so no release-order constraint between API and CLI.