fix: use longhorn-rwx storage for cross-node pipeline scheduling

- StorageClass longhorn-rwx with hard NFS mount (no softerr)
- Prevents Remote I/O errors from share-manager startup race
- RWX allows steps to spread across all 4 cluster nodes
- podAntiAffinity ensures different workflows use different nodes
This commit is contained in:
Celes Renata
2026-04-20 03:23:54 +00:00
parent a2f76cea96
commit 9850dc45b1
+2 -4
View File
@@ -1,10 +1,8 @@
# Woodpecker CI pipeline for Stonks Oracle # Woodpecker CI pipeline for Stonks Oracle
# Translates .github/workflows/build.yml into Woodpecker native format
# Images push to registry.celestium.life/stonks-oracle/<service>:<sha> and :latest # Images push to registry.celestium.life/stonks-oracle/<service>:<sha> and :latest
# #
# Scheduling: Pipeline pods are spread across cluster nodes via agent-level # Storage: longhorn-rwx (RWX) for cross-node step scheduling
# podAntiAffinity (WOODPECKER_BACKEND_K8S_POD_AFFINITY). Resource requests # Scheduling: podAntiAffinity spreads pipeline pods across cluster nodes
# below help the scheduler make balanced placement decisions.
steps: steps:
lint-python: lint-python: