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

Measurements of resource injection overheads #840

Closed
ghost opened this issue May 18, 2021 · 1 comment
Closed

Measurements of resource injection overheads #840

ghost opened this issue May 18, 2021 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@ghost
Copy link

ghost commented May 18, 2021

Feature request

Instrument the dogfooding cluster(s) so that we can start measuring and assessing potential impact of tektoncd/pipeline#3305.

Use case

From the Pipeline issue mentioned above:

Going forward, with the introduction of Tekton Bundles and soon to be other forms of external dependencies, there is a missing concept of the Tekton controllers which is that of "pre-work". That is, reconciliation should not block but reaching out to external services like an image registry is expensive and error prone.

It would be great to start collecting some data to calibrate our understanding of the time and resource costs involved when relying on external services during reconciles. Luckily we've started using bundles in our dogfooding cluster, so we could potentially start collecting that data there.

@ghost ghost added the kind/feature Categorizes issue or PR as related to a new feature. label May 18, 2021
@ghost
Copy link
Author

ghost commented Sep 2, 2021

I'm going to close this one on the basis that the refactoring in tektoncd/pipeline#3305 is moving ahead as part of pipelines' initial remote resolution explorations. We'll figure out how to gather data and draw needed comparisons as part of the experimental controller work rather than tackling this in plumbing I think.

@ghost ghost closed this as completed Sep 2, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

0 participants