Author SHA1 Message Date
woodpecker[bot] 6553b3ba2e WOODPECKER: Changed deployed version to 78613948f5698688723d49a3255f15102b047006 2025-07-27 07:51:13 +00:00
woodpecker[bot] be6995e7ac WOODPECKER: Changed deployed version to 6b0e6486d0e409711b201fc9eb01c899fb5379ec
ci/woodpecker/push/build Pipeline was successful
2025-07-26 18:19:01 +00:00
woodpecker[bot] 6a9e8c426d WOODPECKER: Changed deployed version to a51288df7e430ecb5324f227fd1f5f622f1ea7c3
ci/woodpecker/push/build Pipeline was successful
2025-07-26 18:11:37 +00:00
woodpecker[bot] 1ccf6eeeac WOODPECKER: Changed deployed version to 2bb530126442c9219afbefb89e86607ff6a9cbe6
ci/woodpecker/push/build Pipeline was successful
2025-07-26 18:04:48 +00:00
woodpecker[bot] 0472721177 WOODPECKER: Changed deployed version to 1f57e0ba7f32940d2820b740970130a4cba9f611
ci/woodpecker/push/build Pipeline was successful
2025-07-26 17:53:50 +00:00
woodpecker[bot] c472855e77 WOODPECKER: Changed deployed version to d420e62aac71f203f5f815c443d040a79c6ac69a
ci/woodpecker/push/build Pipeline was successful
2025-07-26 16:30:10 +00:00
woodpecker[bot] b9a4534885 WOODPECKER: Changed deployed version to 9ba8c0951913de8f1df367917a5b959b58c8b34f
ci/woodpecker/push/build Pipeline was successful
2025-07-26 16:24:11 +00:00
woodpecker[bot] 6b07de6b57 WOODPECKER: Changed deployed version to de7040cc0a7f816de02d7176d4f8d0bcb082812f
ci/woodpecker/push/build Pipeline was successful
2025-07-26 16:18:12 +00:00
woodpecker[bot] 2e9897ab8a WOODPECKER: Changed deployed version to 6127e7a19c367f41ecb87e85f7abde3b92bee623
ci/woodpecker/push/build Pipeline was successful
2025-07-26 16:12:31 +00:00
woodpecker[bot] b4db4c12e5 WOODPECKER: Changed deployed version to 88aec64018ddaeab9d41079d65a8018a6f09a5a2
ci/woodpecker/push/build Pipeline was successful
2025-07-26 16:06:28 +00:00
woodpecker[bot] 563161cfc4 WOODPECKER: Changed deployed version to 829e8f09a3e7fd3df6e54357c04409dc7d928262
ci/woodpecker/push/build Pipeline was successful
2025-07-26 16:00:38 +00:00
woodpecker[bot] 02f9f89327 WOODPECKER: Changed deployed version to 75aa55b69899de7d27cf6843682998e0ec84a517
ci/woodpecker/push/build Pipeline was successful
2025-07-26 15:54:44 +00:00
woodpecker[bot] 2a67b60a93 WOODPECKER: Changed deployed version to 532010790d5e58c2bebce7a5178cbab29f70ec7c
ci/woodpecker/push/build Pipeline was successful
2025-07-26 15:48:49 +00:00
woodpecker[bot] ec5ac7216b WOODPECKER: Changed deployed version to 71579de0197e7000c53180676e0d84dc303beacb
ci/woodpecker/push/build Pipeline was successful
2025-07-26 15:42:45 +00:00
woodpecker[bot] 419ea2afdb WOODPECKER: Changed deployed version to d0ae8432afeb148080eee949a989d88a93d88e34
ci/woodpecker/push/build Pipeline was successful
2025-07-26 15:36:54 +00:00
woodpecker[bot] 2c7d07d504 WOODPECKER: Changed deployed version to f6215cd286a566aa984641defa0b956416c04e13
ci/woodpecker/push/build Pipeline was successful
2025-07-26 15:31:16 +00:00
woodpecker[bot] 6a1164704d WOODPECKER: Changed deployed version to 7a8cb55b705f60f954e60830b0bc03dfdc26a91a
ci/woodpecker/push/build Pipeline was successful
2025-07-26 15:25:33 +00:00
woodpecker[bot] 15430760d4 WOODPECKER: Changed deployed version to 1fd5bafdbd6327a9e6fe43067e73bec3b87d6674
ci/woodpecker/push/build Pipeline was successful
2025-07-26 15:19:42 +00:00
woodpecker[bot] 1caf04eb7d WOODPECKER: Changed deployed version to 7919c055af11ee118f0623d370234dc64829ecb7
ci/woodpecker/push/build Pipeline was successful
2025-07-26 15:13:34 +00:00
woodpecker[bot] eabffd3bd3 WOODPECKER: Changed deployed version to 291f8229ac70d079dd3d5eacf6230915d9075b4c
ci/woodpecker/push/build Pipeline was successful
2025-07-26 15:07:54 +00:00
woodpecker[bot] dfa62c2a0b WOODPECKER: Changed deployed version to cedc4c52e1f5c1a663e1524abb85cda35ef08624
ci/woodpecker/push/build Pipeline was successful
2025-07-26 15:00:25 +00:00
woodpecker[bot] 32f1d5a892 WOODPECKER: Changed deployed version to af829bc5bbd5be5561e332ba2c4602e037310057
ci/woodpecker/push/build Pipeline was successful
2025-07-26 14:53:30 +00:00
pikram 701972ae03 Increased healthcheck probes
ci/woodpecker/push/build Pipeline was successful
2025-07-26 14:45:55 +00:00
woodpecker[bot] 0581e6647b WOODPECKER: Changed deployed version to 66e2a0e3b929dbdb72504e93d40020754551c370
ci/woodpecker/push/build Pipeline failed
2025-07-26 14:40:28 +00:00
woodpecker[bot] 776a707f90 WOODPECKER: Changed deployed version to 6bfcbb1c9602d305846058896c20bde4a4669a66
ci/woodpecker/push/build Pipeline was successful
2025-07-26 14:21:05 +00:00
Marcin-Ramotowski b789a8b021 Switch to use multiline script block in pipeline
ci/woodpecker/push/build Pipeline was successful
2025-07-26 16:02:20 +02:00
Marcin-Ramotowski 6808c7176e Created Woodpecker pipeline
ci/woodpecker/push/build Pipeline failed
2025-07-26 15:41:12 +02:00
Marcin-Ramotowski bd629b4244 Removed Jenkins pipeline 2025-07-26 15:41:12 +02:00
6 changed files with 46 additions and 271 deletions
-32
View File
@@ -1,32 +0,0 @@
FROM debian:bookworm-slim
# Zapobiega interaktywnym promptom
ENV DEBIAN_FRONTEND=noninteractive
# Instalacja zależności systemowych
RUN apt-get update && apt-get install -y \
ca-certificates \
curl \
gnupg \
lsb-release \
apt-transport-https \
software-properties-common \
unzip \
bash \
&& rm -rf /var/lib/apt/lists/*
# Instalacja Azure CLI
RUN curl -sL https://aka.ms/InstallAzureCLIDeb | bash
# Instalacja kubectl (najświeższa stabilna wersja)
RUN curl -sLo /usr/local/bin/kubectl https://dl.k8s.io/release/v1.33.1/bin/linux/amd64/kubectl \
&& chmod +x /usr/local/bin/kubectl
# Instalacja kubelogin
RUN curl -sLo /tmp/kubelogin.zip https://github.com/Azure/kubelogin/releases/latest/download/kubelogin-linux-amd64.zip \
&& unzip -j /tmp/kubelogin.zip -d /usr/local/bin \
&& chmod +x /usr/local/bin/kubelogin \
&& rm /tmp/kubelogin.zip
# Domyślna komenda po starcie kontenera
CMD ["bash"]
-86
View File
@@ -1,86 +0,0 @@
pipeline {
agent {
kubernetes {
yamlFile '.jenkins/podTemplate.yaml'
}
}
environment {
RESOURCE_GROUP = 'tst-aks-rg'
CLUSTER_NAME = 'build'
DEPLOY_FILES = 'namespace.yaml secret-store.yaml deploy.yaml ingress.yaml'
NAMESPACE = 'user-microservice'
DEPLOYMENT = 'api'
CLIENT_ID = 'c302726f-fafb-4143-94c1-67a70975574a'
}
stages {
stage('Checkout') {
steps {
container('kubectl') {
checkout scm
}
}
}
stage('Login to Azure & Get Kubeconfig') {
steps {
container('kubectl') {
sh '''
az login --identity --client-id ${CLIENT_ID}
az aks get-credentials --resource-group $RESOURCE_GROUP --name $CLUSTER_NAME --overwrite-existing
kubelogin convert-kubeconfig -l azurecli
'''
}
}
}
stage('Apply Kubernetes Resources') {
steps {
container('kubectl') {
script {
def files = DEPLOY_FILES.tokenize()
for (file in files) {
sh "kubectl apply -f ${file}"
}
}
}
}
}
stage('Verify Deployment') {
steps {
container('kubectl') {
script {
// Waiting until all pods reach "ready" status
sh '''
echo "Waiting for deployment rollout..."
kubectl rollout status deployment/$DEPLOYMENT -n $NAMESPACE --timeout=60s
'''
}
}
}
}
stage('Health Check') {
steps {
container('kubectl') {
script {
// Check if app is healthy
def ingressUrl = "https://user-microservice.marcin00.pl/health"
sh """
echo "Checking app health ${ingressUrl}..."
for i in {1..30}; do
if curl -sf $ingressUrl; then
echo "Health check OK"
exit 0
else
echo "Health check failed. Retry \$i..."
sleep 5
fi
done
echo "Health check failed."
exit 1
"""
}
}
}
}
}
}
-24
View File
@@ -1,24 +0,0 @@
apiVersion: v1
kind: Pod
metadata:
labels:
some-label: jenkins-agent
spec:
containers:
- name: kubectl
image: marcin00.azurecr.io/azure-cli-kubectl:latest
command:
- cat
tty: true
volumeMounts:
- name: workspace-volume
mountPath: /home/jenkins/agent
volumes:
- name: workspace-volume
emptyDir: {}
nodeSelector:
kubernetes.io/os: linux
restartPolicy: Never
+45
View File
@@ -0,0 +1,45 @@
when:
- event: push
branch: woodpecker-deploy
steps:
- name: 'Deploy user microservice'
image: marcin00.azurecr.io/azure-cli-kubectl:latest
environment:
CLIENT_ID: 'c302726f-fafb-4143-94c1-67a70975574a'
CLUSTER_NAME: 'build'
DEPLOY_FILES: 'namespace.yaml secret-store.yaml deploy.yaml ingress.yaml'
DEPLOYMENT: 'api'
HEALTHCHECK_URL: 'https://user-microservice.marcin00.pl/health'
NAMESPACE: 'user-microservice'
RESOURCE_GROUP: 'tst-aks-rg'
commands:
# Login to Azure & Get Kubeconfig
- az login --identity --client-id $CLIENT_ID
- az aks get-credentials --resource-group $RESOURCE_GROUP --name $CLUSTER_NAME --overwrite-existing
- kubelogin convert-kubeconfig -l azurecli
# Apply Kubernetes Resources
- |
for file in $DEPLOY_FILES; do
kubectl apply -f "$file"
done
# Verify Deployment (waiting until all pods reach "ready" status)
- echo "Waiting for deployment rollout..."
- kubectl rollout status deployment/$DEPLOYMENT -n $NAMESPACE --timeout=60s
# Health Check
- |
echo "Checking app health $HEALTHCHECK_URL..."
for i in {1..120}; do
if curl -sf $HEALTHCHECK_URL; then
echo "Health check OK"
exit 0
else
echo "Health check failed. Retry \$i..."
sleep 5
fi
done
echo "Health check failed."
exit 1
-128
View File
@@ -1,128 +0,0 @@
# user-microservice-deploy
Repozytorium **GitOps** dla mikroserwisu [`user-microservice`](../user-microservice). Zawiera
**manifesty Kubernetes** wdrażanej aplikacji oraz **konfiguracje narzędzi CD** (ArgoCD, FluxCD,
`kubectl`) używane w pracy magisterskiej porównującej narzędzia CI/CD do budowania i wdrażania
aplikacji skonteneryzowanych.
Zgodnie z zasadą GitOps stan klastra jest odwzorowaniem zawartości tego repozytorium: potok CI
z repozytorium aplikacji aktualizuje tutaj tag obrazu, a narzędzie CD wprowadza tę zmianę na
klaster (przez synchronizację *pull* w ArgoCD/FluxCD lub przez `kubectl apply` w wariancie
imperatywnym).
---
## Spis treści
- [Rola w architekturze](#rola-w-architekturze)
- [Manifesty Kubernetes](#manifesty-kubernetes)
- [Wariant wdrożenia = branch](#wariant-wdrożenia--branch)
- [Narzędzia CD](#narzędzia-cd)
- [kubectl (Jenkins / Woodpecker)](#kubectl-jenkins--woodpecker)
- [ArgoCD](#argocd)
- [FluxCD](#fluxcd)
- [Argo Workflows](#argo-workflows)
- [Sekrety i tożsamość](#sekrety-i-tożsamość)
- [Powiązanie z repozytorium aplikacji](#powiązanie-z-repozytorium-aplikacji)
---
## Rola w architekturze
```
Potok CI (repo aplikacji) to repozytorium (GitOps) Klaster AKS
───────────────────────── ──────────────────────── ───────────
docker push (tag = SHA) ──▶ commit: "Changed deployed version to <SHA>" ──▶ narzędzie CD
(podmiana image w deploy.yaml) (apply / sync)
```
Historia commitów w tym repozytorium to zapis kolejnych wdrożeń — każdy commit typu
`... Changed deployed version to <SHA>` odpowiada jednemu przebiegowi potoku CI.
## Manifesty Kubernetes
Aplikacja wdrażana jest do namespace `user-microservice`. Zestaw manifestów:
| Plik | Zawartość |
|------|-----------|
| `namespace.yaml` | Namespace `user-microservice` |
| `deploy.yaml` | Deployment + Service dla **MySQL** oraz Deployment + Service dla **API** (to tutaj potok CI podmienia tag obrazu kontenera `api`) |
| `ingress.yaml` | Ingress (NGINX) wystawiający API pod `user-microservice.marcin00.pl` |
| `secret-store.yaml` | `SecretProviderClass` (CSI secrets-store) mapujący sekrety z Azure Key Vault na sekrety K8s |
| `rbac-role.yaml` | `ClusterRoleBinding` dla tożsamości wdrażającej |
> W wariantach **FluxCD** manifesty aplikacji leżą w `apps/user-microservice/`, a konfiguracja
> klastra w `clusters/prod/`. W pozostałych wariantach manifesty znajdują się w katalogu
> głównym repozytorium.
## Wariant wdrożenia = branch
Każdy scenariusz porównawczy (kombinacja narzędzia CI i CD) ma osobny branch:
| Branch | Scenariusz | CI | CD |
|--------|-----------|----|----|
| `master` | — | — | baza manifestów |
| `jenkins-kubernetes` | 1 | Jenkins | `kubectl apply` (potok deploy w Jenkins) |
| `jenkins-argocd-deploy` | 2 | Jenkins | ArgoCD |
| `jenkins-fluxcd-deploy` | 3 | Jenkins | FluxCD |
| `woodpecker-deploy` | 4 | Woodpecker | `kubectl apply` (potok deploy w Woodpecker) |
| `woodpecker-argocd-deploy` | 5 | Woodpecker | ArgoCD |
| `woodpecker-fluxcd-deploy` | 6 | Woodpecker | FluxCD |
| `argo-deploy` | 7 | Argo Workflows | Argo Workflows |
| `argoworkflow-argocd` | 8 | Argo Workflows | ArgoCD |
| `argoworkflow-fluxcd` / `fluxcd` | 9 | Argo Workflows | FluxCD |
## Narzędzia CD
### kubectl (Jenkins / Woodpecker)
Wariant imperatywny „to samo narzędzie do CI i CD". Potok deploy jest wyzwalany commitem do
tego repozytorium i wykonuje sekwencję:
1. logowanie do Azure (managed identity) i pobranie kubeconfig (`az aks get-credentials`
+ `kubelogin`),
2. `kubectl apply` kolejnych manifestów (`namespace`, `secret-store`, `deploy`, `ingress`),
3. `kubectl rollout status` — oczekiwanie na gotowość podów,
4. **health check** aplikacji przez `curl` na `/health` (do skutku lub timeout).
- **Jenkins** — `.jenkins/Jenkinsfile` (+ `Dockerfile`, `podTemplate.yaml`) na branchu
`jenkins-kubernetes`.
- **Woodpecker** — `.woodpecker/build.yaml` na branchu `woodpecker-deploy`.
### ArgoCD
Model GitOps typu *pull*: ArgoCD obserwuje odpowiedni branch tego repozytorium i synchronizuje
manifesty ze stanem klastra. Manifesty w katalogu głównym repo, wdrożenie wyzwalane commitem
potoku CI (podmiana taga obrazu).
### FluxCD
Model GitOps typu *pull* oparty na CRD Fluksa (katalog `clusters/prod/`):
| Plik | Rola |
|------|------|
| `source.yaml` | `GitRepository` — źródło (ten branch repo), odpytywane co 1 min |
| `kustomization.yaml` | `Kustomization` — ścieżka `./apps/user-microservice`, `prune: true`, docelowy namespace |
| `flux-receiver.yaml` | `Receiver` — webhook przyspieszający reakcję na push (bez czekania na interwał) |
| `source.yaml` / `load-balancer.yaml` / `network-policy.yaml` | Dodatkowa konfiguracja klastra (zależnie od wariantu) |
### Argo Workflows
W scenariuszu 7 (branch `argo-deploy`) rolę CD pełni Argo Workflows: `EventSource` w repo
aplikacji nasłuchuje również na webhook z tego repozytorium (endpoint
`user-microservice-deploy`), co pozwala wyzwolić workflow wdrożeniowy po zmianie manifestów.
## Sekrety i tożsamość
- Sekrety aplikacji (`SQLALCHEMY_DATABASE_URI`, hasła MySQL) nie są przechowywane w repo —
pochodzą z **Azure Key Vault** i są montowane do podów przez sterownik CSI `secrets-store`
(`secret-store.yaml`, `SecretProviderClass` `azure-kvname`).
- Uwierzytelnianie do ACR/AKS/Key Vault odbywa się przez **managed identity** (bez haseł).
- Klucz deploy do Gitea oraz `known_hosts` są dostarczane potokom CI jako sekrety narzędzia
CI (nie znajdują się w repozytorium).
## Powiązanie z repozytorium aplikacji
Kod aplikacji, definicje potoków CI oraz analiza wyników pomiarów znajdują się w repozytorium
[`user-microservice`](../user-microservice) — zobacz jego `README.md` po pełny opis architektury,
scenariuszy pomiarowych i mapy branchy.
+1 -1
View File
@@ -81,7 +81,7 @@ spec:
spec: spec:
containers: containers:
- name: api - name: api
image: marcin00.azurecr.io/user-microservice:a79ae2d50f2fc3dfcf976eb2a8ebe32511ae4a33 image: marcin00.azurecr.io/user-microservice:78613948f5698688723d49a3255f15102b047006
ports: ports:
- containerPort: 80 - containerPort: 80
env: env: