Files
gooseek/backend/deploy/k8s/opensandbox.yaml
home 00adac3196
All checks were successful
Build and Deploy GooSeek / build-and-deploy (push) Successful in 3m26s
fix: move sandbox ResourceQuota/LimitRange to gooseek-sandbox namespace
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
2026-03-03 03:14:01 +03:00

73 lines
1.5 KiB
YAML

apiVersion: v1
kind: ServiceAccount
metadata:
name: opensandbox-sa
namespace: gooseek
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: opensandbox-server
namespace: gooseek
labels:
app: opensandbox-server
app.kubernetes.io/name: opensandbox-server
app.kubernetes.io/part-of: gooseek
spec:
replicas: 1
selector:
matchLabels:
app: opensandbox-server
template:
metadata:
labels:
app: opensandbox-server
spec:
serviceAccountName: opensandbox-sa
containers:
- name: opensandbox
image: registry.cn-hangzhou.aliyuncs.com/open_sandbox/server:v1.0.1
ports:
- containerPort: 8080
name: http
env:
- name: SANDBOX_NAMESPACE
value: "gooseek-sandbox"
- name: SANDBOX_DEFAULT_TIMEOUT
value: "30m"
- name: SANDBOX_MAX_CONCURRENT
value: "20"
resources:
requests:
cpu: 200m
memory: 256Mi
limits:
cpu: 1000m
memory: 512Mi
livenessProbe:
httpGet:
path: /health
port: 8080
initialDelaySeconds: 15
periodSeconds: 30
readinessProbe:
httpGet:
path: /health
port: 8080
initialDelaySeconds: 10
periodSeconds: 15
---
apiVersion: v1
kind: Service
metadata:
name: opensandbox-server
namespace: gooseek
spec:
type: ClusterIP
selector:
app: opensandbox-server
ports:
- port: 8080
targetPort: 8080
name: http