Review dependency on naming convention between EKS-A CRDs
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**:
Dependency of EKS Anywhere CRDs is based on naming conventions.
It would be better if there was an explicit link between two objects (label/owner ref)
See: https://github.com/aws/eks-anywhere/pull/1199#discussion_r806272704
**Why is this needed**:
Contributor guide
Research direction
Start by reviewing the EKS Anywhere CRD definitions and the discussion linked from PR #1199, focusing on where object relationships currently depend on names. Determine which CRDs need an explicit label or owner reference, then define how consumers should use it and what tests would verify the relationship.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100