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

chore: Upgrade Spectrum and go-containerregistry #2779

Merged
merged 1 commit into from
Nov 24, 2021
Merged

chore: Upgrade Spectrum and go-containerregistry #2779

merged 1 commit into from
Nov 24, 2021

Conversation

astefanutti
Copy link
Member

@astefanutti astefanutti commented Nov 24, 2021

This PR upgrades Spectrum (the default build strategy on vanilla Kubernetes) to the latest version, that contains an upgraded patched version of go-containerregistry, whose fork is now hosted at https://github.com/container-tools/go-containerregistry.

That new version of go-containerregistry has seen quite a lot of useful improvements compared to the current version.

FWIW, on my laptop, with Minikube, the first build (with dependencies download) of a typical REST Camel K integration takes 25s:

$ kubectl get builds.camel.apache.org
NAME                       PHASE       AGE   STARTED   DURATION        ATTEMPTS
kit-c6f3jaiks20t8nm2oi8g   Succeeded   45s   45s       25.512306317s  

While subsequent builds take around 16s:

$ kubectl get builds.camel.apache.org
NAME                       PHASE       AGE   STARTED   DURATION        ATTEMPTS
kit-c6f3k6qks20t8nm2oi90   Succeeded   31s   31s       16.149875583s 

Which provides a fairly decent user experience, performance wise.

Release Note

chore: Upgrade Spectrum and go-containerregistry

@astefanutti astefanutti merged commit a783131 into apache:main Nov 24, 2021
@astefanutti astefanutti deleted the pr-331 branch November 24, 2021 16:53
@oscerd oscerd mentioned this pull request Jan 20, 2022
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 this pull request may close these issues.

3 participants