Update .gitea/workflows/deploy.yaml
Deploy Dashboard Monitor ke K3s / deploy (push) Failing after 4s Details

This commit is contained in:
Administrator 2026-06-22 17:39:03 +08:00
parent b8aa5a7784
commit 8f695a09eb
1 changed files with 7 additions and 24 deletions

View File

@ -1,32 +1,15 @@
name: Deploy Dashboard Monitor ke K3s
on:
push:
branches:
- main
on: [push]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- name: 1. Tarik Kode dari Repo
uses: actions/checkout@v3
- uses: actions/checkout@v3
- name: 2. Deploy Langsung ke Kubernetes
- name: Deploy via SSH Lokal
run: |
echo "=> Mendownload kubectl resmi..."
curl -LO "https://dl.k8s.io/release/v1.28.2/bin/linux/amd64/kubectl"
chmod +x kubectl
echo "=> Merakit kunci rahasia K3s..."
# Mengubah base64 secret kembali menjadi file yaml
echo "${{ secrets.KUBECONFIG }}" | base64 -d > kubeconfig.yaml
chmod 600 kubeconfig.yaml
echo "=> Mengetes koneksi ke cluster..."
./kubectl --kubeconfig=kubeconfig.yaml get nodes
echo "=> Mengirim perintah deploy..."
./kubectl --kubeconfig=kubeconfig.yaml apply -f dashdot-deploy.yaml
echo "=> Menunggu rollout selesai..."
./kubectl --kubeconfig=kubeconfig.yaml rollout status deployment/dashdot
# SSH ke localhost dan jalankan perintah kubectl langsung di VPS
# Ini mem-bypass masalah Secrets dan Kubeconfig Base64
ssh -o StrictHostKeyChecking=no root@localhost "KUBECONFIG=/etc/rancher/k3s/k3s.yaml kubectl apply -f dashdot-deploy.yaml"
ssh -o StrictHostKeyChecking=no root@localhost "KUBECONFIG=/etc/rancher/k3s/k3s.yaml rollout status deployment/dashdot"