Create generic Forgejo workflow template for Helm and raw manifest deploys #36

New issue

Open

opened 2026-07-25 19:37:19 +00:00 by lab · 0 comments

lab commented

2026-07-25 19:37:19 +00:00

Owner

There are zero .forgejo/workflows/ files. Create a reusable workflow pattern that most services can use with minimal customization.

Two workflow types needed

1. Helm deploy (for services using Helm charts)

name: Deploy {{SERVICE}}
on:
  push:
    paths: ['k3s-ha-cluster/{{SERVICE}}/**']
jobs:
  deploy:
    runs-on: self-hosted
    container:
      image: git.yukselcloud.com/lab/kubectl-node:latest
    steps:
      - uses: actions/checkout@v4
      - name: Setup Kubeconfig
        run: mkdir -p ~/.kube && echo "${{ secrets.KUBECONFIG_DEPLOY }}" > ~/.kube/config
      - name: Helm Upgrade
        run: |
          helm upgrade --install {{SERVICE}} {{CHART}}             --namespace {{NAMESPACE}}             --values k3s-ha-cluster/{{SERVICE}}/values.yaml

2. kubectl apply (for raw manifests)

name: Deploy {{SERVICE}}
on:
  push:
    paths: ['k3s-ha-cluster/{{SERVICE}}/**']
jobs:
  deploy:
    runs-on: self-hosted
    container:
      image: git.yukselcloud.com/lab/kubectl-node:latest
    steps:
      - uses: actions/checkout@v4
      - name: Setup Kubeconfig
        run: mkdir -p ~/.kube && echo "${{ secrets.KUBECONFIG_DEPLOY }}" > ~/.kube/config
      - name: Apply
        run: kubectl apply -n {{NAMESPACE}} -f k3s-ha-cluster/{{SERVICE}}/
      - name: Rollout Restart
        run: kubectl -n {{NAMESPACE}} rollout restart deploy {{DEPLOY_NAME}}

Steps

Create both template variants in k3s-ha-cluster/.forgejo/workflows/
Document which template each service should use
Create per-service workflow files in subsequent issues

There are zero `.forgejo/workflows/` files. Create a reusable workflow pattern that most services can use with minimal customization. ## Two workflow types needed ### 1. Helm deploy (for services using Helm charts) ```yaml name: Deploy {{SERVICE}} on: push: paths: ['k3s-ha-cluster/{{SERVICE}}/**'] jobs: deploy: runs-on: self-hosted container: image: git.yukselcloud.com/lab/kubectl-node:latest steps: - uses: actions/checkout@v4 - name: Setup Kubeconfig run: mkdir -p ~/.kube && echo "${{ secrets.KUBECONFIG_DEPLOY }}" > ~/.kube/config - name: Helm Upgrade run: | helm upgrade --install {{SERVICE}} {{CHART}} --namespace {{NAMESPACE}} --values k3s-ha-cluster/{{SERVICE}}/values.yaml ``` ### 2. kubectl apply (for raw manifests) ```yaml name: Deploy {{SERVICE}} on: push: paths: ['k3s-ha-cluster/{{SERVICE}}/**'] jobs: deploy: runs-on: self-hosted container: image: git.yukselcloud.com/lab/kubectl-node:latest steps: - uses: actions/checkout@v4 - name: Setup Kubeconfig run: mkdir -p ~/.kube && echo "${{ secrets.KUBECONFIG_DEPLOY }}" > ~/.kube/config - name: Apply run: kubectl apply -n {{NAMESPACE}} -f k3s-ha-cluster/{{SERVICE}}/ - name: Rollout Restart run: kubectl -n {{NAMESPACE}} rollout restart deploy {{DEPLOY_NAME}} ``` ## Steps 1. Create both template variants in `k3s-ha-cluster/.forgejo/workflows/` 2. Document which template each service should use 3. Create per-service workflow files in subsequent issues