ci: configura deploy automatico para k3s

This commit is contained in:
Marcus 2026-01-23 17:15:40 -03:00
parent dec58c7c73
commit 82feaaa5b2

View file

@ -8,7 +8,6 @@ on:
jobs: jobs:
build-and-push: build-and-push:
# ... (seu código de build que já funcionou, mantenha igual)
runs-on: docker-ready runs-on: docker-ready
env: env:
DOCKER_API_VERSION: "1.43" DOCKER_API_VERSION: "1.43"
@ -18,20 +17,24 @@ jobs:
steps: steps:
- name: Install Dependencies - name: Install Dependencies
run: apk add --no-cache git docker-cli docker-cli-buildx nodejs run: apk add --no-cache git docker-cli docker-cli-buildx nodejs
- name: Checkout code - name: Checkout code
uses: actions/checkout@v4 uses: actions/checkout@v4
with: with:
fetch-depth: 1 fetch-depth: 1
- name: Set up Docker Buildx - name: Set up Docker Buildx
run: | run: |
docker buildx create --use --driver docker-container --name local-builder || docker buildx use local-builder docker buildx create --use --driver docker-container --name local-builder || docker buildx use local-builder
docker buildx inspect --bootstrap docker buildx inspect --bootstrap
- name: Login to Forgejo Registry - name: Login to Forgejo Registry
uses: docker/login-action@v3 uses: docker/login-action@v3
with: with:
registry: pipe.gohorsejobs.com registry: pipe.gohorsejobs.com
username: bohessefm username: bohessefm
password: ${{ secrets.FORGEJO_TOKEN }} password: ${{ secrets.FORGEJO_TOKEN }}
- name: Build and Push Backend - name: Build and Push Backend
uses: docker/build-push-action@v5 uses: docker/build-push-action@v5
with: with:
@ -42,6 +45,7 @@ jobs:
tags: | tags: |
pipe.gohorsejobs.com/bohessefm/gohorsejobs:latest pipe.gohorsejobs.com/bohessefm/gohorsejobs:latest
pipe.gohorsejobs.com/bohessefm/gohorsejobs:${{ github.sha }} pipe.gohorsejobs.com/bohessefm/gohorsejobs:${{ github.sha }}
- name: Build and Push Backoffice - name: Build and Push Backoffice
uses: docker/build-push-action@v5 uses: docker/build-push-action@v5
with: with:
@ -63,7 +67,6 @@ jobs:
- name: Install Tools (Git & Kubectl) - name: Install Tools (Git & Kubectl)
run: | run: |
apk add --no-cache git curl apk add --no-cache git curl
# Baixa o kubectl manualmente para não depender de Actions externas
curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl" curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl"
chmod +x kubectl chmod +x kubectl
mv kubectl /usr/local/bin/ mv kubectl /usr/local/bin/
@ -73,24 +76,24 @@ jobs:
- name: Deploy to K3s - name: Deploy to K3s
run: | run: |
# Cria o diretório .kube e salva o config do secret # 1. SALVA O CONFIG E EXPORTA A VARIÁVEL
mkdir -p $HOME/.kube echo "${{ secrets.KUBECONFIG }}" > /tmp/kubeconfig
echo "${{ secrets.KUBECONFIG }}" > $HOME/.kube/config chmod 600 /tmp/kubeconfig
chmod 600 $HOME/.kube/config export KUBECONFIG=/tmp/kubeconfig # ISSO AQUI MATA O ERRO DE LOCALHOST
# 1. Deleta e Recria os Segredos no K8s # 2. DELETA E RECRIA OS SEGREDO
kubectl -n gohorsejobsdev delete secret backend-secrets --ignore-not-found kubectl -n gohorsejobsdev delete secret backend-secrets --ignore-not-found
kubectl -n gohorsejobsdev create secret generic backend-secrets \ kubectl -n gohorsejobsdev create secret generic backend-secrets \
--from-literal=DATABASE_URL="${{ vars.DATABASE_URL }}" \ --from-literal=DATABASE_URL="${{ vars.DATABASE_URL }}" \
--from-literal=JWT_SECRET="${{ vars.JWT_SECRET }}" \ --from-literal=JWT_SECRET="${{ vars.JWT_SECRET }}" \
--from-literal=MTU="${{ vars.MTU }}" --from-literal=MTU="${{ vars.MTU }}"
# 2. Aplica os manifestos da pasta k8s/dev # 3. APLICA OS MANIFESTOS
kubectl apply -f k8s/dev/ -n gohorsejobsdev kubectl apply -f k8s/dev/ -n gohorsejobsdev
# 3. Força o restart para pegar a imagem nova (:latest) # 4. RESTARTA OS DEPLOYMENTS
kubectl -n gohorsejobsdev rollout restart deployment gohorse-backend-dev kubectl -n gohorsejobsdev rollout restart deployment gohorse-backend-dev
kubectl -n gohorsejobsdev rollout restart deployment gohorse-backoffice-dev kubectl -n gohorsejobsdev rollout restart deployment gohorse-backoffice-dev
# 4. Verifica o status # 5. VERIFICA O STATUS FINAL
kubectl -n gohorsejobsdev rollout status deployment gohorse-backend-dev kubectl -n gohorsejobsdev rollout status deployment gohorse-backend-dev