build: 更新镜像仓库地址为 docker.oa.unissense.tech
同步所有部署配置和构建脚本中的镜像仓库地址,将原 docker.llm.unissense.tech 替换为新的 docker.oa.unissense.tech,确保部署流程和镜像拉取使用正确的仓库。main
parent
a94206a743
commit
7b76211696
|
|
@ -12,7 +12,7 @@ all-in-one 容器内端口:`80` CRM 前端、`8090` 系统管理前端、`8080
|
|||
## 构建并推送
|
||||
|
||||
```bash
|
||||
docker login docker.llm.unissense.tech -u admin
|
||||
docker login docker.oa.unissense.tech -u admin
|
||||
|
||||
./deploy/build-and-push.sh # all-in-one,镜像名 unis_scc
|
||||
./deploy/build-and-push.sh app
|
||||
|
|
@ -33,7 +33,7 @@ kubectl apply -f deploy/k3s-unis-scc-allinone.yaml
|
|||
kubectl -n unis-scc rollout status deploy/unis-scc
|
||||
|
||||
# 节点访问不了 Harbor:离线导入
|
||||
docker save -o /tmp/unis_scc.tar docker.llm.unissense.tech/public/unis_scc:latest
|
||||
docker save -o /tmp/unis_scc.tar docker.oa.unissense.tech/public/unis_scc:latest
|
||||
scp /tmp/unis_scc.tar node:/tmp/ && ssh node 'k3s ctr images import /tmp/unis_scc.tar'
|
||||
```
|
||||
|
||||
|
|
@ -61,7 +61,7 @@ metadata:
|
|||
namespace: unis-scc
|
||||
type: kubernetes.io/dockerconfigjson
|
||||
stringData:
|
||||
.dockerconfigjson: '{"auths":{"docker.llm.unissense.tech":{"username":"admin","password":"unix@1234"}}}'
|
||||
.dockerconfigjson: '{"auths":{"docker.oa.unissense.tech":{"username":"admin","password":"unix@1234"}}}'
|
||||
```
|
||||
|
||||
### Ingress(k3s 自带 Traefik)
|
||||
|
|
@ -117,7 +117,7 @@ PY
|
|||
`latest` + `imagePullPolicy: IfNotPresent` 组合下,重新导入或重新推送 `latest` **不会**让已在跑的 Pod 换镜像,必须重建 Pod。清单已把镜像钉成具体时间戳 tag(如 `202610301521`)来避免这类"改了没生效",出新版时改这一行或执行:
|
||||
|
||||
```bash
|
||||
kubectl -n unis-scc set image deploy/unis-scc unis-scc=docker.llm.unissense.tech/public/unis_scc:<新TAG>
|
||||
kubectl -n unis-scc set image deploy/unis-scc unis-scc=docker.oa.unissense.tech/public/unis_scc:<新TAG>
|
||||
kubectl -n unis-scc rollout status deploy/unis-scc
|
||||
```
|
||||
|
||||
|
|
@ -158,3 +158,11 @@ curl -s -o - -w '\nHTTP %{http_code}\n' -X POST http://<节点IP>:30092/mcp \
|
|||
```
|
||||
|
||||
镜像没重建前的临时绕法:直接打后端端口 `http://<节点IP>:30091/mcp`。
|
||||
|
||||
公网走的是 `crm.unissense.top`(111.10.202.195 上的 openresty)→ 节点 `:30092` → 容器内 nginx 这条链路。openresty 只把 `Server` 改成了 `openresty`,但路径和 POST 方法都原样转了进来(405 的 HTML 正文就是容器内 nginx 产生的),`X-Bot-*` 头是否透传等上线后再验一次,所以边缘层不用改,只要 Pod 换成含 `location = /mcp` 的镜像即可。判断是哪一层没通,分别打两个地址对比:
|
||||
|
||||
```bash
|
||||
curl -s -o /dev/null -w '域名 -> %{http_code}\n' -X POST https://crm.unissense.top/mcp -H 'Content-Type: application/json' -d '{}'
|
||||
curl -s -o /dev/null -w '节点 -> %{http_code}\n' -X POST http://<节点IP>:30092/mcp -H 'Content-Type: application/json' -d '{}'
|
||||
# 两边都从 405 变 401 = 修复生效;节点通了但域名还是 405 = 去查 openresty 的 location 配置
|
||||
```
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ spec:
|
|||
terminationGracePeriodSeconds: 45
|
||||
containers:
|
||||
- name: unis-scc
|
||||
image: docker.llm.unissense.tech/public/unis_scc:202611021202
|
||||
image: docker.oa.unissense.tech/public/unis_scc:202611021202
|
||||
imagePullPolicy: IfNotPresent
|
||||
ports:
|
||||
- name: crm
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# ============================================================================
|
||||
# unis_scc(UNIS CRM)—— k3s 单镜像 all-in-one 部署
|
||||
#
|
||||
# 镜像:docker.llm.unissense.tech/public/unis_scc:202611021202 (linux/amd64)
|
||||
# 镜像:docker.oa.unissense.tech/public/unis_scc:202611021202 (linux/amd64)
|
||||
# 一个容器里同时跑:
|
||||
# nginx :80 -> CRM 前端静态站点 + /api、/sys 反代
|
||||
# nginx :8090 -> 系统管理前端静态站点 + /api、/sys 反代
|
||||
|
|
@ -64,7 +64,7 @@ spec:
|
|||
terminationGracePeriodSeconds: 45
|
||||
containers:
|
||||
- name: unis-scc
|
||||
image: docker.llm.unissense.tech/public/unis_scc:202611021202
|
||||
image: docker.oa.unissense.tech/public/unis_scc:202611021202
|
||||
# 离线导入场景必须 IfNotPresent,否则仍会去 Harbor 拉取并 ErrImagePull;
|
||||
# 想每次强制拉最新,改成 Always 或把 image 换成时间戳 tag
|
||||
imagePullPolicy: IfNotPresent
|
||||
|
|
|
|||
Loading…
Reference in New Issue