Add status to Cluster object
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
Add some fields to the status for the Cluster that might be useful for a user to get information about the status of their EKS-A cluster object. Below is just an example of what the status object can look like:
```
status:
version: ""
controlPlaneMachineCount: 1
workerNodeGroups:
- machineCount: 1
externalEtcdMachineCount: 1
gitOps:
gitOpsRef: ""
repository: ""
owner: ""
branch: ""
latestCommit: ""
status: pending/synced/paused/unavailable # reflects whether our eks-a controller is syncing with the repository or not
bundlesRef: "" # References a bundle CRD that contains information about all versions of container images that we rely on
licenseRef: ""
```
Contributor guide
Research direction
No files or tests are named. Start by locating the Cluster object and the EKS-A controller's status handling, then review how the proposed GitOps, bundles, and license references relate to the Cluster API. Done means the requested status information has an agreed design and is exposed consistently on the Cluster object.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend-api-design, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100