Open
Conversation
Add an EKS managed add-on status view so operators can review installed add-on versions, status, and health issues from the cluster browser. - map ListAddons and DescribeAddon output into TUI-facing add-on models - add add-on list/detail navigation, filtering, warning states, and help text - document the EKS add-on flow and cover mapping plus Bubble Tea transitions Constraint: Issue #167 asks for status visibility only, not add-on mutation or upgrades. Rejected: Add update/delete actions | destructive or drift-remediation behavior is outside this issue and would require confirmation workflows. Confidence: high Scope-risk: moderate Directive: Do not add add-on mutation actions without type-to-confirm safeguards and separate tests. Tested: env -u GOROOT go test ./... Tested: env -u GOROOT make test Tested: env -u GOROOT make build Related: #167
Contributor
There was a problem hiding this comment.
This PR successfully adds EKS managed add-on status viewing capabilities to the CLI tool. The implementation is well-structured and follows existing patterns throughout the codebase.
Highlights:
- Clean implementation of
ListEKSAddonswith proper pagination handling - Comprehensive test coverage for add-on listing and status detection
- Proper TUI integration with filtering, navigation, and warning styling for degraded add-ons
- Consistent error handling and nil safety checks
The code is production-ready and implements the feature as described in the PR summary.
You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.
nathanhuh
approved these changes
Apr 27, 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
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.
Summary
Add an EKS managed add-on status view so operators can spot unhealthy core add-ons from the cluster browser.
ListEKSAddonsusingListAddonsandDescribeAddonanavigation into add-on list/detail screens with filtering and warning stylingRelated Issues
Closes #167
Validation
env -u GOROOT go test ./...env -u GOROOT make testenv -u GOROOT make buildgit diff --checkChecklist
docs/branch-naming-harness.mddocs/documentation-harness.md)docs/pages updated if architecture, auth, config, or workflow changedNo breaking changes.