deploy: roll the MCP server onto the renamed schema

The running pod predates the table rename and fails every tool that touches the
template tables, so the image is rebuilt as v3 and the Deployment follows it.
The manifest is bumped with it — `imagePullPolicy: IfNotPresent` means
re-pushing the same tag would keep serving the cached layers, so a rebuild needs
a new tag to reach the cluster at all.

Verified by handshake against the running server: `field_list` answers with the
45 library titles.
This commit is contained in:
2026-09-22 16:58:02 +08:00
parent 199e328b48
commit 103b5544ba
+3 -3
View File
@@ -67,7 +67,7 @@ spec:
type: RuntimeDefault
containers:
- name: mcp
image: registry.cn-hangzhou.aliyuncs.com/mcp_skill/paper-doc-mcp:v2
image: registry.cn-hangzhou.aliyuncs.com/mcp_skill/paper-doc-mcp:v3
imagePullPolicy: IfNotPresent
ports:
- name: http
@@ -178,13 +178,13 @@ spec:
# imagePullSecrets: [{name: aliyun-acr}]
# initContainers:
# - name: migrate
# image: registry.cn-hangzhou.aliyuncs.com/mcp_skill/paper-doc-mcp:v2
# image: registry.cn-hangzhou.aliyuncs.com/mcp_skill/paper-doc-mcp:v3
# command: ["alembic", "upgrade", "head"]
# envFrom: [{configMapRef: {name: paper-doc-config}}]
# env: [...] # the same three secret keys as above
# containers:
# - name: api
# image: registry.cn-hangzhou.aliyuncs.com/mcp_skill/paper-doc-mcp:v2
# image: registry.cn-hangzhou.aliyuncs.com/mcp_skill/paper-doc-mcp:v3
# command: ["uvicorn", "app.main:app", "--host", "0.0.0.0", "--port", "8000"]
# ports: [{name: http, containerPort: 8000}]
# envFrom: [{configMapRef: {name: paper-doc-config}}]