Skip to content

feat: add EKS managed addon status view#189

Open
YoungJinJung wants to merge 1 commit intomainfrom
feature/167-eks-addon-status-view
Open

feat: add EKS managed addon status view#189
YoungJinJung wants to merge 1 commit intomainfrom
feature/167-eks-addon-status-view

Conversation

@YoungJinJung
Copy link
Copy Markdown
Contributor

Summary

Add an EKS managed add-on status view so operators can spot unhealthy core add-ons from the cluster browser.

  • adds ListEKSAddons using ListAddons and DescribeAddon
  • maps add-on version, status, owner/publisher, role ARN, and health issues into a TUI model
  • adds cluster-level a navigation into add-on list/detail screens with filtering and warning styling
  • updates README and docs for the expanded EKS browser flow

Related Issues

Closes #167

Validation

  • env -u GOROOT go test ./...
  • env -u GOROOT make test
  • env -u GOROOT make build
  • git diff --check

Checklist

  • Scope is focused
  • Branch name follows docs/branch-naming-harness.md
  • Documentation harness reviewed (docs/documentation-harness.md)
  • README updated if user-facing behavior changed
  • Relevant docs/ pages updated if architecture, auth, config, or workflow changed
  • Tests/validation included
  • Breaking changes documented

No breaking changes.

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
Copy link
Copy Markdown
Contributor

@amazon-q-developer amazon-q-developer Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 ListEKSAddons with 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat: add EKS managed addon status view

2 participants