Skip to content
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

Time-to-readiness reporting tool #69

Closed
ulucinar opened this issue Feb 28, 2023 · 0 comments · Fixed by #71
Closed

Time-to-readiness reporting tool #69

ulucinar opened this issue Feb 28, 2023 · 0 comments · Fixed by #71
Assignees

Comments

@ulucinar
Copy link
Contributor

ulucinar commented Feb 28, 2023

We've previously defined a simple metric named time-to-readiness, which basically captures the time it takes for a managed resource to acquire the Ready=True condition from the time recored in metadata.creationTimestamp.

A standalone tool for reporting the time-to-readiness values observed on the managed resources in a cluster will help us in collecting feedback from the community and also in future performance regression tests we would like to implement in provider repositories.

We can reuse some logic already available in this PR.

We should also consider exposing this metric as a Prometheus metric (topic of a different work stream).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant