removed workflow

.gitea/workflows/publish-helm.yaml

@@ -1,57 +0,0 @@
-name: Helm Publish
-
-on:
-  push:
-    branches:
-      - main
-  workflow_dispatch:
-
-jobs:
-  publish:
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Install Helm
-        run: |
-          set -euo pipefail
-          curl -sSL https://get.helm.sh/helm-v3.15.0-linux-amd64.tar.gz -o /tmp/helm.tgz
-          tar xzf /tmp/helm.tgz -C /tmp
-          install /tmp/linux-amd64/helm /usr/local/bin/helm
-
-      - name: Install helm cm-push plugin
-        run: |
-          set -euo pipefail
-          helm plugin install https://github.com/chartmuseum/helm-push
-
-      - name: Lint and package chart
-        run: |
-          set -euo pipefail
-          ##helm lint .
-          helm dependency update . || true
-          helm package . -d /tmp
-
-      - name: Push chart to Gitea Helm registry
-        env:
-          HELM_REPO_URL: "https://gitea.apilab.us/api/packages/cscott/helm"
-          HELM_REPO_NAME: "gitea-helm"
-          HELM_USER: "cscott"
-          HELM_PASSWORD: "${{ secrets.HELM_PASSWORD }}"
-        run: |
-          set -euo pipefail
-          helm repo add "$HELM_REPO_NAME" "$HELM_REPO_URL" \
-            --username "$HELM_USER" \
-            --password "$HELM_PASSWORD"
-
-          NAME="$(grep '^name:' Chart.yaml | awk '{print $2}')"
-          YAML_VERSION="$(grep '^version:' Chart.yaml | awk '{print $2}')"
-          CHART_TGZ="/tmp/${NAME}-${YAML_VERSION}.tgz"
-          if [ ! -f "$CHART_TGZ" ]; then
-            echo "Expected packaged chart not found: $CHART_TGZ"
-            ls -l /tmp
-            exit 1
-          fi
-
-          helm cm-push "$CHART_TGZ" "$HELM_REPO_NAME"

README.md

@@ -1,5 +1,5 @@
 # Gitea Actions Helm Chart
-
+---
 This helm chart serves as the way to deploy the Gitea [act-runners](https://gitea.com/gitea/act_runner) alongside a running Gitea instance.  
 It serves as a standalone chart and does not rely on Gitea to be present in the same environment, however it needs to be able to reach a Gitea instance to function.  
 The parameters which can be used to customize the deployment are described below, check those out if you want to see if something is supported.  

templates/statefulset.yaml

@@ -91,6 +91,9 @@ spec:
         - name: dind
           image: "{{ include "gitea.actions.dind.image" . }}"
           imagePullPolicy: {{ .Values.statefulset.dind.pullPolicy }}
+          args:
+            - "--iptables=false"
+            - "--ip-forward=false"
           env:
             - name: DOCKER_HOST
               value: tcp://127.0.0.1:2376

values.yaml

@@ -46,7 +46,7 @@ statefulset:
   tolerations: []
   affinity: {}
   extraVolumes: []
-  #securityContext: {}
+  securityContext: {}
 
   actRunner:
     registry: "docker.gitea.com"
@@ -83,9 +83,11 @@ statefulset:
 
     # If the container keeps crashing in your environment, you might have to add the `DOCKER_IPTABLES_LEGACY` environment variable.
     # See https://github.com/docker-library/docker/issues/463#issuecomment-1881909456
-    extraEnvs: []
+    extraEnvs:
       #  - name: "DOCKER_IPTABLES_LEGACY"
       #    value: "1"
+      - name: DOCKER_OPTS
+        value: "--iptables=false --ip-forward=false"
 
   persistence:
     size: 1Gi