Move EKS-A and EKS-D resources to management cluster
Open
area/cli
kind/enhancement
team/cli
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
**What would you like to be added**:
Move the eksa and eksd resources to management cluster.
**Why is this needed**:
Contributor guide
Research direction
The issue names no files, tests, or entry points; begin by locating the eksa and eksd resource definitions and the management-cluster reconciliation path. Confirm the intended resource ownership and verify that both resources are moved to the management cluster without breaking existing cluster behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100