Skip to content

Conversation

@hanleyyin
Copy link
Collaborator

This also updates the docker/build-push-action to v6, as v2 does not support the provenance option

- name: Login to Staging ECR
uses: docker/login-action@v1
with:
registry: 105154636954.dkr.ecr.us-east-1.amazonaws.com
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you mean to use the env variable here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't realize that these were the same value, good catch. Thinking back, I think REGISTRY makes more sense than REPO for the env variable names, since these are the registries that contain the repositories.

@hanleyyin hanleyyin force-pushed the update_on_release_pr branch from bd0996d to 98f90c6 Compare March 25, 2025 16:03
tags: |
${{ env.TAG_BASE }}:${{steps.tag.outputs.tag}}-amd64
push: true
- name: Build and push manifest list
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does this need to be a separate step now?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These all need to be a separate step because to my knowledge, there's no other way to tag the individual architectures in addition to the manifest list.

Images must be pushed to your repository before you create the Docker manifest.

https://docs.aws.amazon.com/AmazonECR/latest/userguide/docker-push-multi-architecture-image.html (this doc link uses docker manifest instead of docker buildx but the same applies)

This also updates the docker/build-push-action to v6, as v2 does not
support the provenance option

Signed-off-by: HanleyYin <[email protected]>
@cert-manager-prow
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@cert-manager-prow cert-manager-prow bot merged commit 6edb336 into cert-manager:main Mar 28, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants