Fix: attach latest tag to images - DockerHub synchronize with GHCR #1086
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
This PR solves the problem of not pushing the latest tag to docker hub. Pushing this tag is mandatory as discussed in the PR #1079
Which issue(s) this PR fixes:
Fixes #1068
GitHub action jobs - than ran on my personal credentials with tag v23.1.1 - this is just a temporary tag to check the creation of images.
Fluentd Job
Fluent-Bit Job - In Progress
Fluent Operator Job
Verification of images pushed to docker hub:
fluent-operator
fluentbit
fluentd
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.:
As per this containers/image#447 discussion --additional-tags is only copying to docker-archive.
Also copying manifests is also not helping