Add a limiter for pushing images

[sa02]

In environments where multiple registries exist for the purpose of security with scan and promotion pipelines, imgpkg presents an issue where intermediate pipelines become overloaded due to the inability to properly stage.

Right now, we have a team pushing 300+ images to a pipeline that can handle 50 images at a time.

As a base solution, the ability to add a delay per image push would help significantly, in order to stagger the full deployment. Example below:

imgpkg push $IMAGE -d 10 
# -d = delay 
# 10 = 10 seconds

---

Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help work on this issue.

[github-actions]

This issue is being marked as stale due to a long period of inactivity and will be closed in 5 days if there is no response.

[praveenrewar]

@sa02 Apologies for missing this for so many days 😞
If I understand you issue correctly, imgpkg is being used concurrently to push 300+ images to the same registry and the registry can handle only 50 pushes at a time?

[github-actions]

This issue is being marked as stale due to a long period of inactivity and will be closed in 5 days if there is no response.