fix: helm lint error

This commit is contained in:
sirily11 2026-01-27 22:54:26 +08:00
parent 78ef8322ff
commit fa2f8d4a48
No known key found for this signature in database
GPG Key ID: 210EC8A2FB4FB9CB
2 changed files with 12 additions and 18 deletions

View File

@ -41,18 +41,15 @@ service:
ingress:
enabled: true
className: nginx
domain: "my-clawdbot.example.com"
annotations:
cert-manager.io/cluster-issuer: letsencrypt-prod
nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
nginx.ingress.kubernetes.io/proxy-read-timeout: "3600"
nginx.ingress.kubernetes.io/proxy-send-timeout: "3600"
nginx.ingress.kubernetes.io/websocket-services: "clawdbot"
hosts:
- host: my-clawdbot.example.com
paths:
- path: /
pathType: Prefix
tls:
- secretName: clawdbot-tls
hosts:
- my-clawdbot.example.com
enabled: true
secretName: clawdbot-tls
certManager:
enabled: true
issuer: letsencrypt-prod

View File

@ -65,20 +65,17 @@ resources:
ingress:
enabled: true
className: nginx
domain: "assistant.example.com"
annotations:
cert-manager.io/cluster-issuer: letsencrypt-prod
nginx.ingress.kubernetes.io/proxy-read-timeout: "3600"
nginx.ingress.kubernetes.io/proxy-send-timeout: "3600"
nginx.ingress.kubernetes.io/websocket-services: "clawdbot"
hosts:
- host: assistant.example.com
paths:
- path: /
pathType: Prefix
tls:
- secretName: clawdbot-tls
hosts:
- assistant.example.com
enabled: true
secretName: clawdbot-tls
certManager:
enabled: true
issuer: letsencrypt-prod
affinity:
nodeAffinity: