-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add PerClusterResourceCounts to GitRepo status #3209
Conversation
a722192
to
df8e482
Compare
@aruiz14 - this is still flagged as draft 🤔 |
Yes. It depends on another PR being reviewed, but Github it's not nice showing stacked PRs |
df8e482
to
ace6f56
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, pending resolution of a couple of doubts :)
ace6f56
to
6e42b0c
Compare
6e42b0c
to
aa1ea74
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, although I'd be more comfortable with an additional review from the team.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Refers to #3186
This PR extends the current public API to add a new field to every GitRepoStatus:
perClusterResourceCounts
, which is a map of related resource counts by cluster ID.It uses the new status field added to BundleDeploymentStatus by Add resourceCounts and incomplete state to BundleDeploymentStatus #3203
In addition, it removes the dependency on the GitRepo's
status.summary
field, which is just a pre-calculated summary of BundleDeployment statuses, which was then aggregated and used to assign a resource state. Instead, I've changed it to use the actual per-BundleDeployment state since it's available.