maxbirkin/gooseek
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: move sandbox ResourceQuota/LimitRange to gooseek-sandbox namespace
All checks were successful
Build and Deploy GooSeek / build-and-deploy (push) Successful in 3m26s
Details

Browse Source 
Kustomize was overriding namespace to gooseek for all resources including
ResourceQuota and LimitRange meant for gooseek-sandbox. This caused
CPU quota exceeded errors blocking all new pod creation (used 26.3/16 cores).
Split sandbox-scoped resources into opensandbox-sandbox-ns.yaml applied
directly, and deploy.sh now cleans up misplaced quota from gooseek ns.

Made-with: Cursor
This commit is contained in:
home
2026-03-03 03:14:01 +03:00
parent 52134df4d1
commit 00adac3196
3 changed files with 94 additions and 85 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
backend/deploy/k8s/deploy.sh
View File

@@ -82,6 +82,16 @@ if command -v envsubst &> /dev/null && [ -f "$ENV_FILE" ]; then
envsubst < "$SCRIPT_DIR/monitoring.yaml" > "$SCRIPT_DIR/_generated_monitoring.yaml"
fi
# Apply sandbox-namespace resources separately (not via kustomize to preserve namespace)
echo ""
echo "=== Applying sandbox namespace resources ==="
kubectl apply -f "$SCRIPT_DIR/sandbox-namespace.yaml"
kubectl apply -f "$SCRIPT_DIR/opensandbox-sandbox-ns.yaml"
# Clean up misplaced quota/limitrange from gooseek namespace (legacy fix)
kubectl delete resourcequota sandbox-quota -n gooseek --ignore-not-found=true 2>/dev/null || true
kubectl delete limitrange sandbox-limits -n gooseek --ignore-not-found=true 2>/dev/null || true
# Apply kustomization
echo ""
echo "=== Applying K8s manifests ==="