setting corresponding branch name as tag

amagioss · Jan 29, 2024 · 5d362b2 · 5d362b2
1 parent 678a09a
commit 5d362b2
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/.github/workflows/build-main.yml → .github/workflows/build-branch.yml b/.github/workflows/build-main.yml → .github/workflows/build-branch.yml
@@ -1,12 +1,12 @@
-name: Build Main Branch
+name: Build Branch
 
 on:
   push:
     branches:
       - main
 
 jobs:
-  build-main:
+  build-branch:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout Code
@@ -39,4 +39,4 @@ jobs:
           context: .
           push: true
           tags: |
-            ghcr.io/${{ github.repository }}/k8slv:${{ github.ref_name }}-snapshot
+            ghcr.io/${{ github.repository }}/k8slv:${{ github.ref_name }}
diff --git a/k8s/deploy-slv-operator.yaml b/k8s/deploy-slv-operator.yaml
@@ -135,7 +135,7 @@ spec:
       serviceAccountName: slv-controller
       containers:
       - name: slv-controller
-        image: ghcr.io/amagimedia/slv/k8slv:latest # Use the version tag corresponding to the version of SLV used with the CR
+        image: ghcr.io/amagimedia/slv/k8slv:main # Use the specific version tag (main branch releases might be unstable) corresponding to the version of SLV used with the CR
         resources:
           limits:
             cpu: "1" # 1 CPU should be fairly enough for SLV Controller