aws-samples / aws-samples/appmod-blueprints
KRO resource groups — align naming with clusterName
- Dominant language
- Shell
- Stars
- 105
- Forks
- 62
- Avg merge
- 11h 17m
- Merged PRs (30d)
- 76
Description
**Parent:** #584
**Priority:** Medium
KRO ResourceGroups use `resourcePrefix` for ECR repos, S3 buckets, IAM roles, capability roles. Align with the clusterName-based naming convention used by infrastructure resources.
**Files:**
- `kro/resource-groups/manifests/cicd-pipeline/cicd-pipeline.yaml`
- `kro/resource-groups/manifests/ray-service/ray-service.yaml`
- `kro/resource-groups/manifests/eks/rg-eks.yaml`
- `kro/resource-groups/manifests/eks/rg-eks-vpc.yaml`
- `kro/resource-groups/manifests/appmod-service.yaml`
Contributor guide
Research direction
Review the five listed manifests under kro/resource-groups/manifests and compare their resourcePrefix usage with the clusterName-based naming convention used by infrastructure resources. Update the ECR, S3, IAM, and capability-role naming consistently across cicd-pipeline, ray-service, EKS, EKS VPC, and appmod-service ResourceGroups; done means all listed resources follow the clusterName convention.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100