Have a way to retrigger only one overlay instead of rebuilding all overlays if only one failed to push to container registry.

[pacospace]

Is your feature request related to a problem? Please describe.
As Developer,

I have 10 overlays, but after 10/10 builds, one failed to push because write access was missing. Later we give write privilegies to the pipeline and we need to redeliver the same tag that would trigger again all 10 builds.

Describe the solution you'd like
OPTION 1: Have a way to retrigger only one overlay instead of rebuilding all overlays if only one failed.
OPTION 2: Introduce a check to verify write privileges are enabled with the secret-pusher before starting the pipeline (currently we check only if the repo is created on quay)

Describe alternatives you've considered

Additional context
Issue is the tag name, maybe overlay-tag as discussed with @harshad16

[goern]

/kind feature
/priority important-longterm

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[sesheta]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[harshad16]

/lifecycle frozen