ci: configura deploy automatico para k3s
This commit is contained in:
parent
2805268826
commit
0ff3731b72
1 changed files with 12 additions and 10 deletions
|
|
@ -76,26 +76,28 @@ jobs:
|
|||
|
||||
- name: Deploy to K3s
|
||||
run: |
|
||||
# 1. CRIA O ARQUIVO E EXPORTA NO MESMO BLOCO
|
||||
# 1. CRIA O ARQUIVO DE CONFIGURAÇÃO
|
||||
echo "${{ secrets.KUBECONFIG }}" > /tmp/kubeconfig
|
||||
chmod 600 /tmp/kubeconfig
|
||||
export KUBECONFIG=/tmp/kubeconfig
|
||||
|
||||
# Criamos um alias local para facilitar a escrita e garantir o arquivo
|
||||
alias k="kubectl --kubeconfig=/tmp/kubeconfig"
|
||||
|
||||
# 2. TESTA A CONEXÃO
|
||||
# 2. TESTA A CONEXÃO FORÇADA
|
||||
echo "Testando conexão com o cluster..."
|
||||
kubectl cluster-info || exit 1
|
||||
k cluster-info || { echo "Falha ao conectar no cluster! Verifique seu KUBECONFIG secret."; exit 1; }
|
||||
|
||||
# 3. ATUALIZA OS SEGREDO
|
||||
kubectl -n gohorsejobsdev delete secret backend-secrets --ignore-not-found
|
||||
kubectl -n gohorsejobsdev create secret generic backend-secrets \
|
||||
k -n gohorsejobsdev delete secret backend-secrets --ignore-not-found
|
||||
k -n gohorsejobsdev create secret generic backend-secrets \
|
||||
--from-literal=DATABASE_URL="${{ vars.DATABASE_URL }}" \
|
||||
--from-literal=JWT_SECRET="${{ vars.JWT_SECRET }}" \
|
||||
--from-literal=MTU="${{ vars.MTU }}"
|
||||
|
||||
# 4. APLICA E RESTARTA
|
||||
kubectl apply -f k8s/dev/ -n gohorsejobsdev
|
||||
kubectl -n gohorsejobsdev rollout restart deployment gohorse-backend-dev
|
||||
kubectl -n gohorsejobsdev rollout restart deployment gohorse-backoffice-dev
|
||||
k apply -f k8s/dev/ -n gohorsejobsdev
|
||||
k -n gohorsejobsdev rollout restart deployment gohorse-backend-dev
|
||||
k -n gohorsejobsdev rollout restart deployment gohorse-backoffice-dev
|
||||
|
||||
# 5. STATUS FINAL
|
||||
kubectl -n gohorsejobsdev rollout status deployment gohorse-backend-dev
|
||||
k -n gohorsejobsdev rollout status deployment gohorse-backend-dev
|
||||
Loading…
Reference in a new issue