-
Notifications
You must be signed in to change notification settings - Fork 175
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
chore: refine the labels and annotations #8178
Conversation
leon-inf
commented
Sep 20, 2024
•
edited
Loading
edited
- Remove the component-replicas annotation key from Pods
- Change the value of generation patched to ITS objects from Cluster to Component
- Pass the cluster uuid through a new cluster-uid annotation key
c270597
to
2ad939f
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #8178 +/- ##
==========================================
- Coverage 61.15% 61.08% -0.08%
==========================================
Files 354 354
Lines 40969 40908 -61
==========================================
- Hits 25054 24988 -66
- Misses 13654 13655 +1
- Partials 2261 2265 +4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
0c220eb
to
a6da8f8
Compare
Comp2CompDefs map[string]string `json:"comp2CompDefs,omitempty"` // {compName: compDefName} | ||
Name string `json:"name,omitempty"` // the name of the component w/o clusterName prefix | ||
FullCompName string `json:"fullCompName,omitempty"` // the full name of the component w/ clusterName prefix | ||
CompDefName string `json:"compDefName,omitempty"` // the name of the componentDefinition | ||
Generation string |
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.
I'm curious why some fields don't have JSON tags defined. This feels like a code smell.
1b51e91
to
b946529
Compare
/approve |