fix

README.md

@@ -1,92 +1,9 @@
-# Native Charts
+# Native charts
 
+一些常用的helm chart，用于快速部署服务到Kubernetes集群。
 
+## 部署 native 集群服务
 
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://gitlab.glm.ai/ai-search/native-charts.git
-git branch -M main
-git push -uf origin main
 ```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://gitlab.glm.ai/ai-search/native-charts/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+helm install test-ng -n app ./chart --set service.name=test-ng --set service.image=nginx:latest --set service.port=80 --set ingress.enabled=true --set ingress.host=test-ng.ai-native.glm.ai 
+```

chart/.helmignore

@@ -0,0 +1,23 @@
+# Patterns to ignore when building packages.
+# This supports shell glob matching, relative path matching, and
+# negation (prefixed with !). Only one pattern per line.
+.DS_Store
+# Common VCS dirs
+.git/
+.gitignore
+.bzr/
+.bzrignore
+.hg/
+.hgignore
+.svn/
+# Common backup files
+*.swp
+*.bak
+*.tmp
+*.orig
+*~
+# Various IDEs
+.project
+.idea/
+*.tmproj
+.vscode/ 

chart/Chart.yaml

@@ -0,0 +1,6 @@
+apiVersion: v2
+name: service-chart
+description: A Helm chart for deploying services
+type: application
+version: 0.1.0
+appVersion: "1.0.0" 

chart/INSTALL.md

@@ -0,0 +1,110 @@
+# 服务部署Helm Chart安装指南
+
+本文档提供了使用此Helm Chart部署服务的详细步骤。
+
+## 安装前准备
+
+1. 确保已安装Helm 3.2.0+
+2. 确保有权限访问Kubernetes集群
+3. 准备好自定义的values.yaml文件
+
+## 基本安装
+
+使用默认配置安装Chart:
+
+```bash
+helm install my-release ./chart
+```
+
+## 使用自定义配置安装
+
+1. 创建自定义values文件，例如`my-values.yaml`
+2. 编辑配置文件设置所需参数
+3. 安装Chart:
+
+```bash
+helm install my-release ./chart -f my-values.yaml
+```
+
+## 常用配置示例
+
+### 部署简单服务
+
+```yaml
+service:
+  name: my-app
+  image: myapp:1.0.0
+  port: 8080
+```
+
+### 部署带环境变量的服务
+
+```yaml
+service:
+  name: my-app
+  image: myapp:1.0.0
+  port: 8080
+
+env:
+  - name: ENV
+    value: production
+  - name: DEBUG
+    value: "false"
+```
+
+### 暴露服务到内网
+
+```yaml
+serviceConfig:
+  exposeToIntranet: true
+```
+
+### 禁用Ingress
+
+```yaml
+ingress:
+  enabled: false
+```
+
+## 验证安装
+
+安装后，使用以下命令验证部署是否成功：
+
+```bash
+# 检查Pod是否正常运行
+kubectl get pods -l app=my-app -n app
+
+# 检查Service是否创建成功
+kubectl get svc -n app
+
+# 如果启用了Ingress，检查Ingress是否创建成功
+kubectl get ingress -n app
+```
+
+## 卸载
+
+使用以下命令卸载Chart:
+
+```bash
+helm uninstall my-release
+```
+
+## 故障排除
+
+如果遇到部署问题，请尝试：
+
+1. 检查Pod状态和日志
+   ```bash
+   kubectl get pods -n app
+   kubectl logs <pod-name> -n app
+   ```
+
+2. 检查服务状态
+   ```bash
+   kubectl describe svc <service-name> -n app
+   ```
+
+3. 检查Ingress状态
+   ```bash
+   kubectl describe ingress <ingress-name> -n app
+   ``` 

chart/README.md

@@ -0,0 +1,58 @@
+# 服务部署Helm Chart
+
+这个Helm Chart用于快速部署服务到Kubernetes集群。
+
+## 前提条件
+
+- Kubernetes 1.19+
+- Helm 3.2.0+
+
+## 安装Chart
+
+```bash
+# 使用默认配置安装
+helm install my-release ./chart
+
+# 使用自定义values文件安装
+helm install my-release ./chart -f values-custom.yaml
+
+# 使用--set覆盖单个配置
+helm upgrade --install test-ng -n app ./chart --set service.name=test-ng --set service.image=nginx:latest --set service.port=80 --set ingress.enabled=true --set ingress.host=test-ng.ai-native.glm.ai 
+```
+
+## 卸载Chart
+
+```bash
+helm uninstall my-release
+```
+
+## 配置参数
+
+以下表格列出了此Chart的可配置参数及其默认值。
+
+| 参数 | 描述 | 默认值 |
+|------|------|--------|
+| `service.name` | 服务名称 | `my-service` |
+| `service.image` | 服务镜像 | `nginx:latest` |
+| `service.port` | 服务端口 | `8080` |
+| `service.replicas` | 服务副本数 | `1` |
+| `service.namespace` | 服务部署的命名空间 | `app` |
+| `service.imagePullPolicy` | 镜像拉取策略 | `IfNotPresent` |
+| `service.imagePullSecrets` | 镜像拉取密钥 | `[{name: uhub}]` |
+| `resources.enabled` | 是否启用资源限制 | `false` |
+| `resources.limits.cpu` | CPU资源限制 | `1` |
+| `resources.limits.memory` | 内存资源限制 | `1Gi` |
+| `resources.requests.cpu` | CPU资源请求 | `500m` |
+| `resources.requests.memory` | 内存资源请求 | `512Mi` |
+| `env` | 环境变量列表 | `[]` |
+| `ingress.enabled` | 是否启用Ingress | `true` |
+| `ingress.className` | Ingress类名 | `ack-nginx-private` |
+| `ingress.host` | 访问域名（必须是ai-native.glm.ai的子域） | `myservice.ai-native.glm.ai` |
+| `ingress.tls.enabled` | 是否启用TLS | `true` |
+| `ingress.tls.secretName` | TLS密钥名称 | `ai-native-glm-ai-tls` |
+| `serviceConfig.exposeToIntranet` | 是否暴露到内网 | `false` |
+| `serviceConfig.annotations` | 内网LoadBalancer注解 | 见values.yaml |
+
+## 示例
+
+请参考`values-example.yaml`文件获取完整的配置示例。 

chart/examples/realtime-server.yaml

@@ -0,0 +1,39 @@
+# realtime-server部署配置示例
+service:
+  name: realtime-server
+  image: uhub.service.ucloud.cn/chatglm/realtime-server-qingyan/ai-aliyun:20250331113845-98e4d564
+  port: 8080
+  replicas: 2
+  namespace: app
+
+resources:
+  enabled: true
+  limits:
+    cpu: 2
+    memory: 2Gi
+  requests:
+    cpu: 1
+    memory: 1Gi
+
+env:
+  - name: ENV_NAME
+    value: production
+  - name: E2E_MODEL_URL
+    value: https://open.bigmodel.cn/api/paas
+  - name: E2E_MODEL_KEY
+    value: glm-4o-audio-250111-qingyan
+  - name: TOS_ACCESS_KEY
+    value: AKLTMzI4NjM0ZjIwNGUxNGQ5NGEwMzhkYmNjMGE0NTEwMWM
+  - name: TOS_SECRET_KEY
+    value: WWpCbE9ETmpObVU1TjJVeU5EZzVNemhoWXpjNE9ETmlaREZsTURFMVlqWQ==
+
+ingress:
+  enabled: true
+  className: ack-nginx-private
+  host: realtime-server.ai-native.glm.ai
+  tls:
+    enabled: true
+    secretName: ai-native-glm-ai-tls
+
+serviceConfig:
+  exposeToIntranet: true 

chart/templates/NOTES.txt

@@ -0,0 +1,14 @@
+感谢使用服务部署Chart！
+
+您的应用程序 {{ .Values.service.name }} 已成功部署。
+
+{{- if .Values.ingress.enabled }}
+应用可通过以下域名访问:
+  https://{{ .Values.ingress.host }}
+{{- end }}
+
+{{- if .Values.serviceConfig.exposeToIntranet }}
+您的服务已配置为LoadBalancer类型并暴露到内网。
+要获取服务IP，请运行以下命令:
+  kubectl get svc {{ .Values.service.name }}-svc -n {{ .Values.service.namespace }} -o jsonpath='{.status.loadBalancer.ingress[0].ip}'
+{{- end }} 

chart/templates/_helpers.tpl

@@ -0,0 +1,8 @@
+{{/* Validate domain name */}}
+{{- define "validateDomain" -}}
+{{- $parts := splitList "." .Values.ingress.host -}}
+{{- $baseHost := join "." (slice $parts 1 (len $parts)) -}}
+{{- if ne $baseHost "ai-native.glm.ai" -}}
+{{- fail "域名必须是ai-native.glm.ai的子域名" -}}
+{{- end -}}
+{{- end -}} 

chart/templates/deployment.yaml

@@ -0,0 +1,45 @@
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: {{ .Values.service.name }}
+  namespace: {{ .Values.service.namespace }}
+  labels:
+    app: {{ .Values.service.name }}
+spec:
+  replicas: {{ .Values.service.replicas }}
+  selector:
+    matchLabels:
+      app: {{ .Values.service.name }}
+  strategy:
+    type: Recreate
+  template:
+    metadata:
+      labels:
+        app: {{ .Values.service.name }}
+    spec:
+      containers:
+        - name: {{ .Values.service.name }}
+          image: {{ .Values.service.image }}
+          imagePullPolicy: {{ .Values.service.imagePullPolicy }}
+          ports:
+            - containerPort: {{ .Values.service.port }}
+              name: http
+              protocol: TCP
+          {{- if .Values.env }}
+          env:
+{{ toYaml .Values.env | indent 12 }}
+          {{- end }}
+          {{- if .Values.resources.enabled }}
+          resources:
+            limits:
+              cpu: {{ .Values.resources.limits.cpu }}
+              memory: {{ .Values.resources.limits.memory }}
+            requests:
+              cpu: {{ .Values.resources.requests.cpu }}
+              memory: {{ .Values.resources.requests.memory }}
+          {{- end }}
+      {{- with .Values.service.imagePullSecrets }}
+      imagePullSecrets:
+{{ toYaml . | indent 8 }}
+      {{- end }}
+      restartPolicy: Always 

chart/templates/ingress.yaml

@@ -0,0 +1,29 @@
+{{- if .Values.ingress.enabled -}}
+{{- template "validateDomain" . -}}
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+  name: {{ .Values.service.name }}-ingress
+  namespace: {{ .Values.service.namespace }}
+  labels:
+    ingress-controller: nginx
+spec:
+  ingressClassName: {{ .Values.ingress.className }}
+  rules:
+    - host: {{ .Values.ingress.host }}
+      http:
+        paths:
+          - backend:
+              service:
+                name: {{ .Values.service.name }}-svc
+                port:
+                  number: {{ .Values.service.port }}
+            path: /
+            pathType: ImplementationSpecific
+  {{- if .Values.ingress.tls.enabled }}
+  tls:
+    - hosts:
+        - {{ .Values.ingress.host }}
+      secretName: {{ .Values.ingress.tls.secretName }}
+  {{- end }}
+{{- end }} 

chart/templates/service.yaml

@@ -0,0 +1,25 @@
+apiVersion: v1
+kind: Service
+metadata:
+  name: {{ .Values.service.name }}-svc
+  namespace: {{ .Values.service.namespace }}
+  {{- if and .Values.serviceConfig.exposeToIntranet .Values.serviceConfig.annotations }}
+  annotations:
+    {{- range $key, $value := .Values.serviceConfig.annotations }}
+    {{ $key }}: {{ $value }}
+    {{- end }}
+  {{- end }}
+spec:
+  {{- if .Values.serviceConfig.exposeToIntranet }}
+  type: LoadBalancer
+  {{- else }}
+  type: ClusterIP
+  {{- end }}
+  ports:
+    - name: http
+      port: {{ .Values.service.port }}
+      protocol: TCP
+      targetPort: {{ .Values.service.port }}
+  selector:
+    app: {{ .Values.service.name }}
+  sessionAffinity: None 

chart/values-example.yaml

@@ -0,0 +1,64 @@
+# 服务配置示例
+service:
+  # 服务名称
+  name: realtime-test
+  # 服务镜像
+  image: uhub.service.ucloud.cn/chatglm/realtime-server-qingyan/ai-aliyun:20250331113845-98e4d564
+  # 服务端口
+  port: 8080
+  # 服务副本数
+  replicas: 1
+  # 服务部署的命名空间
+  namespace: app
+  # 镜像拉取策略
+  imagePullPolicy: IfNotPresent
+  # 镜像拉取密钥
+  imagePullSecrets:
+    - name: uhub
+
+# 服务资源限制
+resources:
+  enabled: true
+  limits:
+    cpu: 1
+    memory: 1Gi
+  requests:
+    cpu: 500m
+    memory: 512Mi
+
+# 环境变量
+env:
+  - name: ENV_NAME
+    value: live-server
+  - name: E2E_MODEL_URL
+    value: https://open.bigmodel.cn/api/paas
+  - name: VIDEO_CHAT_URL
+    value: http://172.18.80.175:5001
+  - name: E2E_MODEL_KEY
+    value: glm-4o-audio-250111-qingyan
+
+# Ingress配置
+ingress:
+  # 是否启用Ingress
+  enabled: true
+  # Ingress类名
+  className: ack-nginx-private
+  # 访问域名
+  host: realtime-test.ai-native.glm.ai
+  # TLS配置
+  tls:
+    enabled: true
+    secretName: ai-native-glm-ai-tls
+
+# Service配置
+serviceConfig:
+  # 是否暴露到内网
+  exposeToIntranet: false
+  # 内网LoadBalancer注解
+  annotations:
+    service.beta.kubernetes.io/alibaba-cloud-loadbalancer-address-type: intranet
+    service.beta.kubernetes.io/alibaba-cloud-loadbalancer-master-zoneid: cn-beijing-i
+    service.beta.kubernetes.io/alibaba-cloud-loadbalancer-name: jenins-service
+    service.beta.kubernetes.io/alibaba-cloud-loadbalancer-resource-group-id: rg-aek26rjnpkxxomy
+    service.beta.kubernetes.io/alibaba-cloud-loadbalancer-slave-zoneid: cn-beijing-g
+    service.beta.kubernetes.io/alibaba-cloud-loadbalancer-vswitch-id: vsw-2zeaejp7a0o5ftt8mspoo 

chart/values.yaml

@@ -0,0 +1,58 @@
+# 服务配置
+service:
+  # 服务名称
+  name: my-service
+  # 服务镜像
+  image: nginx:latest
+  # 服务端口
+  port: 8080
+  # 服务副本数
+  replicas: 1
+  # 服务部署的命名空间
+  namespace: app
+  # 镜像拉取策略
+  imagePullPolicy: IfNotPresent
+  # 镜像拉取密钥
+  imagePullSecrets:
+    - name: uhub
+
+# 服务资源限制（可选）
+resources:
+  enabled: false
+  limits:
+    cpu: 1
+    memory: 1Gi
+  requests:
+    cpu: 500m
+    memory: 512Mi
+
+# 环境变量
+env: []
+# - name: ENV_NAME
+#   value: production
+
+# Ingress配置
+ingress:
+  # 是否启用Ingress
+  enabled: false
+  # Ingress类名
+  className: ack-nginx-private
+  # 访问域名（必须是ai-native.glm.ai的子域）
+  host: myservice.ai-native.glm.ai
+  # TLS配置
+  tls:
+    enabled: true
+    secretName: ai-native-glm-ai-tls
+
+# Service配置
+serviceConfig:
+  # 是否暴露到内网（默认为ClusterIP）
+  exposeToIntranet: false
+  # 内网LoadBalancer注解
+  annotations:
+    service.beta.kubernetes.io/alibaba-cloud-loadbalancer-address-type: intranet
+    service.beta.kubernetes.io/alibaba-cloud-loadbalancer-master-zoneid: cn-beijing-i
+    service.beta.kubernetes.io/alibaba-cloud-loadbalancer-name: jenins-service
+    service.beta.kubernetes.io/alibaba-cloud-loadbalancer-resource-group-id: rg-aek26rjnpkxxomy
+    service.beta.kubernetes.io/alibaba-cloud-loadbalancer-slave-zoneid: cn-beijing-g
+    service.beta.kubernetes.io/alibaba-cloud-loadbalancer-vswitch-id: vsw-2zeaejp7a0o5ftt8mspoo 

demo.yaml

@@ -0,0 +1,128 @@
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: realtime-test-wanglu
+  namespace: app
+  labels:
+    kubepi.org/name: realtime-test-wanglu
+spec:
+  replicas: 1
+  selector:
+    matchLabels:
+      kubepi.org/name: realtime-test-wanglu
+  strategy:
+    type: Recreate
+  template:
+    metadata:
+      labels:
+        kubepi.org/name: realtime-test-wanglu
+    spec:
+      containers:
+        - name: realtime-server
+          image: uhub.service.ucloud.cn/chatglm/realtime-server-qingyan/ai-aliyun:20250331113845-98e4d564
+          imagePullPolicy: IfNotPresent
+          ports:
+            - containerPort: 8080
+              name: http
+              protocol: TCP
+          env:
+            - name: MODEL_ERROR_LARK_URL
+              value: https://open.feishu.cn/open-apis/bot/v2/hook/f5e0fa31-6de9-47f0-801f-7d75f2b0e790
+            - name: ENV_NAME
+              value: live-server-wanglu
+            - name: E2E_MODEL_URL
+              value: https://open.bigmodel.cn/api/paas
+            - name: VIDEO_CHAT_URL
+              value: http://172.18.80.175:5001
+            - name: E2E_MODEL_KEY
+              value: glm-4o-audio-250111-qingyan
+            - name: ENV
+              value: fc
+            - name: TOS_ACCESS_KEY
+              value: AKLTMzI4NjM0ZjIwNGUxNGQ5NGEwMzhkYmNjMGE0NTEwMWM
+            - name: TOS_SECRET_KEY
+              value: WWpCbE9ETmpObVU1TjJVeU5EZzVNemhoWXpjNE9ETmlaREZsTURFMVlqWQ==
+            - name: VIDEO_MODEL_MAX_SECONDS
+              value: '120'
+            - name: E2E_DEBUG_URL
+              value: https://open.feishu.cn/open-apis/bot/v2/hook/4c421a2b-4d6d-48c9-b008-32926b4681b9
+            - name: E2E_DEBUG_BADCASE_URL
+              value: https://open.feishu.cn/open-apis/bot/v2/hook/4c421a2b-4d6d-48c9-b008-32926b4681b9
+            - name: VIDEO_DEBUG_URL
+              value: https://open.feishu.cn/open-apis/bot/v2/hook/b2f4d33a-a237-4f63-9022-3c89e8402e07
+            - name: VIDEO_DEBUG_BADCASE_URL
+              value: https://open.feishu.cn/open-apis/bot/v2/hook/b2f4d33a-a237-4f63-9022-3c89e8402e07
+            - name: VIDEO_CHAT_URL_TEST
+              value: http://172.18.69.119:8081
+            - name: VIDEO_PASSIVE_RESAMPLE_RULES
+              value: 50%:4,75%:4,100%:8
+            - name: ASR_APPID
+              value: '1899415256'
+            - name: ASR_CLUSTER
+              value: volcengine_streaming_ja
+            - name: ASR_ACCESS_TOKEN
+              value: 5NQpYoV144_FH86LHnxc1PcAlso-_wDN
+            - name: SYNTHESIS_URL
+              value: ws://172.20.67.26:8000/v1/ws/audio/speech
+            - name: SYNTHESIS_MODEL_KEY
+              value: glm-4o-tts-ws-250101-biz
+            - name: SYNTHESIS_AUTH_TOKEN
+              value: rhlUrsJBGLkouNpzed9kymB3jT7iUyqAwTWoriymcx33BuNdgI0aSs2sZsEnjLv0
+            - name: OPEN_TELEMETRY_SERVICE_NAME
+              value: chatglm-ai-e2e-chat-test
+            - name: VIDEO_CHAT_TGI_MODEL_KEY
+              value: glm-4o-video-250101-qingyan-staging
+            - name: E2E_MODEL_BEARER_TOKEN
+              value: 5eadecd1630e4cee8e73f9472855e7eb.irqSqrjxXCEGhoMo
+            - name: MODEL_INPUT_ASR_CLIENT_TYPE
+              value: normalASR
+      imagePullSecrets:
+        - name: uhub
+      restartPolicy: Always
+---
+apiVersion: v1
+kind: Service
+metadata:
+  name: realtime-srv-wanglu
+  namespace: app
+spec:
+  internalTrafficPolicy: Cluster
+  ipFamilies:
+    - IPv4
+  ipFamilyPolicy: SingleStack
+  ports:
+    - name: http
+      port: 8080
+      protocol: TCP
+      targetPort: 8080
+  selector:
+    kubepi.org/name: realtime-test-wanglu
+  sessionAffinity: None
+  type: ClusterIP
+---
+
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+  labels:
+    ingress-controller: nginx
+  name: realtime-server-test-wanglu
+  namespace: app
+spec:
+  ingressClassName: ack-nginx-private
+  rules:
+    - host: realtime-test-wanglu.ai-native.glm.ai
+      http:
+        paths:
+          - backend:
+              service:
+                name: realtime-srv-wanglu
+                port:
+                  number: 8080
+            path: /
+            pathType: ImplementationSpecific
+  tls:
+    - hosts:
+        - realtime-test-wanglu.ai-native.glm.ai
+      secretName: ai-native-glm-ai-tls
+