From 32e083129b5443bd221ab9c533e86e528ebabe3c Mon Sep 17 00:00:00 2001
From: Chris Oloff <chris@uber5.com>
Date: Thu, 21 May 2026 21:17:16 +0200
Subject: [PATCH] Revert "experimentally set tag name (will fail)"

This reverts commit 13327bad6f05e1e0881f70e4577fdc3f7cf33503.
---
 entrypoint.sh | 10 ----------
 1 file changed, 10 deletions(-)

diff --git a/entrypoint.sh b/entrypoint.sh
index 1117c24..bad6245 100755
--- a/entrypoint.sh
+++ b/entrypoint.sh
@@ -46,15 +46,5 @@ kubectl --kubeconfig /tmp/k3s.yaml kustomize "/tmp/${KUST_CONFIG}" | sed "s/kust
 echo "UPDATED YAML:"
 cat /tmp/manifests.yaml
 echo "applying..."
-
-# if we have FORGEJO_REF_NAME beginning with "v", then set the image to a tag with value FORGEJO_REF_NAME.
-if [ -n "$FORGEJO_REF_NAME" ] && [[ "$FORGEJO_REF_NAME" == v* ]]; then
-  echo "FORGEJO_REF_NAME starts with v, setting image tag to $FORGEJO_REF_NAME"
-  # sed -i "s|image: myapp:latest|image: myapp:$FORGEJO_REF_NAME|g" /tmp/manifests.yaml
-  kubectl kustomize /tmp/${KUST_CONFIG} edit set image myapp=myapp:$FORGEJO_REF_NAME
-else
-  echo "FORGEJO_REF_NAME does not start with v, leaving image tag as is"
-fi
-
 kubectl --kubeconfig /tmp/k3s.yaml apply -f - </tmp/manifests.yaml
 echo "Done applying kustomized manifests at ${KUST_CONFIG}, success"