sz11zs/hello-cicd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: using env for kubeconfig
Some checks failed
CI/CD Pipeline popravak / build (push) Successful in 1m44s
Details
CI/CD Pipeline popravak / deploy (push) Failing after 1m17s
Details

Browse Source
This commit is contained in:
sz11zs
2026-05-03 10:19:15 +02:00
parent 9969093c91
commit 6d84f34159
1 changed files with 9 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
.gitea/workflows/ci.yml
View File

@@ -64,10 +64,14 @@ jobs:
sed -i "s|image:.*|image: $IMAGE:$TAG|" k8s/deployment.yaml sed -i "s|image:.*|image: $IMAGE:$TAG|" k8s/deployment.yaml
- name: Deploy na k3s - name: Deploy na k3s
env:
KUBECONFIG: ./kubeconfig
run: | run: |
# KLJUČNA PROMJENA: Dodajemo --kubeconfig putanju u svaku naredbu # Prvo provjeravamo postoji li datoteka (za svaki slučaj)
kubectl --kubeconfig=$HOME/.kube/config apply -f k8s/ --validate=false ls -l ./kubeconfig
# Provjera statusa s istom putanjom # Pokrećemo deploy koristeći varijablu okruženja
kubectl --kubeconfig=$HOME/.kube/config rollout status deployment/hello-cicd \ kubectl apply -f k8s/ --validate=false
-n student-sz11zs --timeout=120s
# Provjera statusa
kubectl rollout status deployment/hello-cicd -n student-sz11zs --timeout=120s