Move container to GitHub Packages

.github/workflows/release.yaml

@@ -1,26 +1,31 @@
-name: ci
+name: Release
 on:
   push:
     branches: [main]
   release:
     types: [published]
 
+env:
+  IMAGE_NAME: ghcr.io/${{ github.repository }}
+
 jobs:
-  docker:
+  container:
     runs-on: ubuntu-latest
     steps:
     - name: Set up QEMU
       uses: docker/setup-qemu-action@v1
     - name: Set up Docker Buildx
       uses: docker/setup-buildx-action@v1
-    - name: Login to DockerHub
-      uses: docker/login-action@v1
+
+    - name: Log in to the container registry
+      uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
       with:
-        registry: cr.b8s.dev
-        username: ${{ secrets.REGISTRY_USERNAME }}
-        password: ${{ secrets.REGISTRY_PASSWORD }}
-    - name: Build and push
-      uses: docker/build-push-action@v2
+        registry: ghcr.io
+        username: ${{ github.actor }}
+        password: ${{ secrets.GITHUB_TOKEN }}
+
+    - name: Build and push Docker image
+      uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
       with:
         push: true
-        tags: cr.b8s.dev/library/rollingpin:${{ github.ref_name }}
+        tags: ${{ env.IMAGE_NAME }}:latest,${{ env.IMAGE_NAME }}:${{ github.ref_name }}

README.md

@@ -70,8 +70,8 @@ roleRef:
 on Kubernetes. Just ensure you set the `serviceAccountName` in your pod spec to
 match the Service Account you created for `rollingpin`.
 
-Containers can either by built yourself, or pulled from our registry:
+Containers can either by built yourself, or pulled from GitHub Packages:
 
 ```
-cr.b8s.dev/library/rollingpin:v1.1.1
+ghcr.io/blackieops/rollingpin:v1.2.0
 ```