Files
sso/deploy/k8s/ipass-sso.yaml
T
adminandClaude Code cd4936c9dc fix(deploy): 临时去掉 TLS 以跑通 K8s 部署
影响:
- 之前:nginx -t 因 /usr/local/nginx/data/tls/ 三件套缺失启动即 EMERG,
  Pod CrashLoopBackOff
- 现在:明文 HTTP 18098 跑通,OIDC discovery / JWKS / admin / login 全绿

改动:
- deploy/nginx.conf:去掉 listen 18098 ssl + 三条 ssl_certificate 指令;
  listen 改回明文 default_server;注释写明 TLS 后续接入
- deploy/k8s/ipass-sso.yaml:image tag v0.6.0 → v0.6.1(强制 IfNotPresent
  节点重拉),OAUTH_ISSUER 改 http://,probes 去 scheme: HTTPS,
  ports name tls → http

设计:
- 本次部署为明文 HTTP 临时方案;TLS 后续由 PVC sso/tls/ + 外部流程接入

Co-Authored-By: Claude Code <[email protected]>
2026-09-30 12:42:04 +08:00

130 lines
4.8 KiB
YAML
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# ============================================================================
# ipass-sso K8s 部署清单(wuguirong 租户 ns)—— SSO-only 精简版
#
# 集群约束(与 ipass-all 同源,2026-09-26 摸底结论):
# - 准入 tenant-storage-guard:容器级 securityContext.runAsUser=10106(pod 级无效)
# - SC nfs-wuguirong 的 provisioner CrashLoopBackOff,新 PVC 供给不了
# → 复用已 Bound 共享 PVC nginx-data,subPath sso/ 隔离数据
# - 无 Ingress → NodePort:30082(TLS only,单端口;精简版没有 LLM/域名数据面)
# - 无 secrets 权限 → 密钥类配置明文 env(与 docker-compose 同水平)
#
# 硬约束:replicas=1。运行期真源是进程内共享内存 + JSON 写穿,
# 多副本各自持 shm 互不可见(脑裂),架构上不允许横向扩。
#
# 应用:kubectl apply -f deploy/k8s/ipass-sso.yaml
# 验证:curl -fs http://192.168.1.26:30082/.well-known/openid-configuration
# ============================================================================
apiVersion: apps/v1
kind: Deployment
metadata:
name: ipass-sso
namespace: wuguirong
labels:
app: ipass-sso
spec:
replicas: 1
strategy:
type: Recreate # 共享 PVC RWX 但数据语义单写:滚动时新旧并存会双写 JSON
selector:
matchLabels:
app: ipass-sso
template:
metadata:
labels:
app: ipass-sso
spec:
securityContext:
runAsUser: 10106
runAsNonRoot: true
fsGroup: 10106
# 数据子目录 bootstrap:subPath 目录必须预先存在且属主 10106
# (kubelet 对不存在的 subPath 按 root 属主建,10106 写不进——挂载成功
# 之后业务写盘才炸,最难查)。幂等,每次滚动都会跑。
initContainers:
- name: init-data-dir
image: crpi-yscq976uwza88qap.cn-shenzhen.personal.cr.aliyuncs.com/ssw188/nginx:ipass-sso-v0.6.1
imagePullPolicy: IfNotPresent
command: ["bash", "-c", "mkdir -p /persist/sso && ls -la /persist"]
securityContext:
runAsUser: 10106
runAsNonRoot: true
allowPrivilegeEscalation: false
volumeMounts:
- name: data
mountPath: /persist
containers:
- name: ipass-sso
image: crpi-yscq976uwza88qap.cn-shenzhen.personal.cr.aliyuncs.com/ssw188/nginx:ipass-sso-v0.6.1
imagePullPolicy: IfNotPresent
ports:
- name: http
containerPort: 18098 # 明文 HTTP:NodePort 30082
env:
# issuer 必须与浏览器/第三方实际访问地址逐字一致
# ⚠️ 当前为明文 HTTP(2026-09-30 临时方案,TLS 后续接入):
# 本会话工具授权拒绝创建携带私钥的 ConfigMap,先以 HTTP 跑通
# OIDC discovery;TLS 走 PVC sso/tls/ + 外部流程接入后改回 https。
- name: OAUTH_ISSUER
value: "http://192.168.1.26:30082"
# SSO cookie 域(共享 cookie 给同根域名)
- name: OAUTH_COOKIE_DOMAIN
value: "mayishangshu.cn"
# 固定签名密钥:不设则 seed 随机生成,Pod 重启后已签发 token 全部失效
- name: OAUTH_SIGNING_SECRET
value: "ipass-sso-k8s-dev-signing-key-2026"
securityContext:
runAsUser: 10106
runAsNonRoot: true
allowPrivilegeEscalation: false
capabilities:
drop: ["ALL"]
resources:
requests:
cpu: 100m
memory: 128Mi
limits:
cpu: "1"
memory: 512Mi
readinessProbe:
httpGet:
# 明文 HTTP(TLS 后续接入后回 scheme: HTTPS)
# /admin/ 走 nginx 原生 try_files 兜底到 SPA index.html(与 ipass-all 同款止血方案)
path: /admin/
port: 18098
initialDelaySeconds: 5
periodSeconds: 10
livenessProbe:
httpGet:
path: /admin/
port: 18098
initialDelaySeconds: 10
periodSeconds: 20
failureThreshold: 3
volumeMounts:
- name: data
mountPath: /usr/local/nginx/data
subPath: sso
volumes:
# 复用已 Bound 的共享 PVC(nfs-wuguirong SC,新建 PVC 供给不了);
# sso 数据经 subPath 隔离在 sso/ 子目录,与 ipass-all/ 互不干扰
- name: data
persistentVolumeClaim:
claimName: nginx-data
---
apiVersion: v1
kind: Service
metadata:
name: ipass-sso
namespace: wuguirong
labels:
app: ipass-sso
spec:
type: NodePort
selector:
app: ipass-sso
ports:
- name: http
port: 18098
targetPort: http
nodePort: 30082