|
| 1 | +name: Docker publish |
| 2 | + |
| 3 | +# Tag-based image release. Pushing a semver tag (e.g. v0.5.0) builds the |
| 4 | +# operator image multi-arch, pushes it to GHCR under this repo's name, and |
| 5 | +# signs it with cosign. This is the same shape as the legacy v1alpha1 release |
| 6 | +# process, retargeted at ghcr.io/<owner>/<repo> via the built-in GITHUB_TOKEN |
| 7 | +# (no Docker Hub secrets needed). |
| 8 | +# |
| 9 | +# Release order: push the tag FIRST (this builds ghcr.io/.../etcd-operator:<tag>), |
| 10 | +# then publish the GitHub release for that tag — release-assets.yml renders the |
| 11 | +# install manifests pointing at this image. |
| 12 | + |
| 13 | +on: |
| 14 | + push: |
| 15 | + tags: [ 'v*.*.*' ] |
| 16 | + |
| 17 | +env: |
| 18 | + REGISTRY: ghcr.io |
| 19 | + # github.repository is <owner>/<repo>, e.g. cozystack/etcd-operator |
| 20 | + IMAGE_NAME: ${{ github.repository }} |
| 21 | + |
| 22 | +jobs: |
| 23 | + build: |
| 24 | + runs-on: ubuntu-22.04 |
| 25 | + permissions: |
| 26 | + contents: read |
| 27 | + packages: write |
| 28 | + # Needed for the keyless cosign identity challenge (sigstore/fulcio). |
| 29 | + id-token: write |
| 30 | + |
| 31 | + steps: |
| 32 | + - name: Checkout repository |
| 33 | + uses: actions/checkout@v4 |
| 34 | + |
| 35 | + - name: Install cosign |
| 36 | + uses: sigstore/cosign-installer@v3.5.0 |
| 37 | + |
| 38 | + - name: Set up Docker Buildx |
| 39 | + uses: docker/setup-buildx-action@v3.3.0 |
| 40 | + |
| 41 | + - name: Log into registry ${{ env.REGISTRY }} |
| 42 | + uses: docker/login-action@v3.2.0 |
| 43 | + with: |
| 44 | + registry: ${{ env.REGISTRY }} |
| 45 | + username: ${{ github.actor }} |
| 46 | + password: ${{ secrets.GITHUB_TOKEN }} |
| 47 | + |
| 48 | + - name: Extract Docker metadata |
| 49 | + id: meta |
| 50 | + uses: docker/metadata-action@v5.5.1 |
| 51 | + with: |
| 52 | + images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }} |
| 53 | + # Pin the published tag to the exact git ref (e.g. v0.5.0). This is |
| 54 | + # the SAME source release-assets.yml uses for the IMG it bakes into |
| 55 | + # the install manifest (its RELEASE_TAG is github.ref_name too), so |
| 56 | + # the image that ships and the image the manifest references are |
| 57 | + # provably identical. Don't rely on metadata-action's implicit |
| 58 | + # default: it also emits a moving `latest` and its default tag set is |
| 59 | + # easy to misread — explicit keeps the publish/manifest contract clear. |
| 60 | + tags: | |
| 61 | + type=raw,value=${{ github.ref_name }} |
| 62 | +
|
| 63 | + - name: Build and push Docker image |
| 64 | + id: build-and-push |
| 65 | + uses: docker/build-push-action@v6 |
| 66 | + with: |
| 67 | + context: . |
| 68 | + push: true |
| 69 | + tags: ${{ steps.meta.outputs.tags }} |
| 70 | + labels: ${{ steps.meta.outputs.labels }} |
| 71 | + platforms: linux/amd64,linux/arm64 |
| 72 | + cache-from: type=gha |
| 73 | + cache-to: type=gha,mode=max |
| 74 | + |
| 75 | + - name: Sign the published Docker image |
| 76 | + env: |
| 77 | + TAGS: ${{ steps.meta.outputs.tags }} |
| 78 | + DIGEST: ${{ steps.build-and-push.outputs.digest }} |
| 79 | + run: echo "${TAGS}" | xargs -I {} cosign sign --yes {}@${DIGEST} |
0 commit comments