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

Non Parallel Re-Tagger Sequence #5928

Open
dhodun opened this issue Jun 2, 2021 · 0 comments
Open

Non Parallel Re-Tagger Sequence #5928

dhodun opened this issue Jun 2, 2021 · 0 comments
Labels
area/modules area/tag kind/friction Issues causing user pain that do not have a workaround kind/todo implementation task/epic for the skaffold team planning/Q4-21 Q4 2021 planning priority/p1 High impact feature/bug. source/partnerships

Comments

@dhodun
Copy link
Contributor

dhodun commented Jun 2, 2021

Expected behavior

Re-tagging existing images in my GCR repo could/should be in parallel

Actual behavior

It seems to be serialized, I'm not 100% sure if its because each container belongs in its own config / module or always behaves this way

Information

  • Skaffold version: 1.24.1
  • Operating system: MacOS
  • Installed via: curl
  • Contents of skaffold.yaml:

Each Docker container, built on Google Cloud Build, has its own config/module.

Removing the individual container names, but ran with -v debug and sha256 tagger

INFO[0001] Tags generated in 249.431 micro seconds
.
. *a bunch of containers are found by SHA and retagged to 'latest'
.
INFO[0015] Cache check completed in 13.659 seconds
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/modules area/tag kind/friction Issues causing user pain that do not have a workaround kind/todo implementation task/epic for the skaffold team planning/Q4-21 Q4 2021 planning priority/p1 High impact feature/bug. source/partnerships
Projects
None yet
Development

No branches or pull requests

3 participants