-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
reinstate hive health metrics #32603
reinstate hive health metrics #32603
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
02d445d
to
b7af21f
Compare
3281e3b
to
a285970
Compare
/test |
ah, CI found a legitimate issue - marking as draft for now, sorry for the noise |
2901d35
to
4d7d063
Compare
/test |
4d7d063
to
02140ac
Compare
/test |
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.
Whoops!
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
02140ac
to
06ba3fa
Compare
/test |
Moves the healthv2 implementation to hive/health to get rid of the somewhat ugly v2 part of the pkg name, and to give some logical structure. Signed-off-by: David Bimmler <david.bimmler@isovalent.com>
Pulling this bugfix in manually to ensure we don't hit race conditions after the next commit. Signed-off-by: David Bimmler <david.bimmler@isovalent.com>
With the introduction of the hive module health metric publisher in a subsequent path, a precondition of the node manager EmitStatus test will break: the test assumes the node manager to be the only writer to the status table. Without this patch, a race occurs. Since it seems likely that the set of default hive cells will grow (and that they may want to update their status too) change the test so that it no longer assumes exclusivity. It now looks specifically at its own status, and uses revisions to understand when the status changes. Signed-off-by: David Bimmler <david.bimmler@isovalent.com>
Somewhere in the move from pkg/hive to cilium/hive we lost the module health metrics. Add them back in the new form of a query on the status table, and add a test. Fixes: 2311f3d (treewide: rebase on cilium/hive) Signed-off-by: David Bimmler <david.bimmler@isovalent.com>
This ensures that logging output of the metrics job and the rest of the health subsystem are piped through the same logging mechanism. In addition, unexport what need not be exported, and avoid some amount of stuttering in "health.HealthTableName", for example. Signed-off-by: David Bimmler <david.bimmler@isovalent.com>
06ba3fa
to
79e1b96
Compare
/test |
@marseel if you could take a look not only at the vendor stuff but also the mildly adapted test, I believe you've recently worked on the bg node sync stuff (in |
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.
Looks good from vendor point of view, one non-blocking idea for the node manager test.
As part of #32020, the hive module health metrics were accidentially dropped. Reinstate them in a new form, and add a test for the functionality.