-
Notifications
You must be signed in to change notification settings - Fork 345
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
Configure parallel container image layers push based on CPU quota #3340
Comments
@astefanutti please assign it to me. |
This was referenced Jun 13, 2022
This issue has been automatically marked as stale due to 90 days of inactivity. |
I think this can be closed. Any leftover by any chance? |
Yes, it's been addressed by #3366. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The CPU resources allocated to the operator can significantly impact the integration build time.
Following #2837, which makes the operator aware of the CPU quota set on the operator container, the underlying container image push implementation should be configured accordingly.
For instance, the new option introduced in google/go-containerregistry#803 should be surfaced in Spectrum1, defaulted according to the operator container CPU quota, and passed to go-containerregistry2.
1: https://github.com/container-tools/spectrum/blob/8f8efa4592a2891dd9c1efa3f031f73a36862a93/pkg/builder/options.go#L5-L16
2: https://github.com/container-tools/spectrum/blob/8f8efa4592a2891dd9c1efa3f031f73a36862a93/pkg/builder/build.go#L55
The text was updated successfully, but these errors were encountered: