From 61a6c143ad776236a2b49e2643a577c467f13b31 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E5=BC=A0=E6=96=8C?= <259278618@qq.com> Date: Sat, 23 May 2026 17:12:26 +0800 Subject: [PATCH] dockerfile --- .gitea/workflows/deploy.yml | 33 +++++++++++++++------------------ 1 file changed, 15 insertions(+), 18 deletions(-) diff --git a/.gitea/workflows/deploy.yml b/.gitea/workflows/deploy.yml index 4a26454..0390a14 100644 --- a/.gitea/workflows/deploy.yml +++ b/.gitea/workflows/deploy.yml @@ -7,31 +7,28 @@ jobs: deploy: runs-on: ubuntu-latest env: - K3S_HOST: ${{ secrets.K3S_HOST }} # 你已配置的K3s服务器地址 + # 从组织级Secrets读取,不用在仓库重复配置 + K3S_HOST: ${{ secrets.K3S_HOST }} APP_NAME: ${{ gitea.repo_name }} - # 核心修改1:跳过镜像推送(避免依赖DockerHub密钥),直接部署 - # 若后续要推送镜像,再配置REGISTRY和Docker密钥 steps: - - uses: gitea/actions/checkout@v4 + - name: 拉取代码 + uses: actions/checkout@v4 - # 核心修改2:删除Docker Buildx/登录/推送步骤(避免认证报错) - # 若后续需要构建推送镜像,再恢复这部分并配置Docker密钥 - - # 核心修改3:修复SSH部署步骤(解决/k8s/deploy.yaml不存在) - name: SSH部署K3s run: | mkdir -p ~/.ssh - # 适配你已配置的密钥名K3S_SSH_KEY(原K3S_PEM_KEY改为K3S_SSH_KEY) + # 写入组织配置的SSH私钥 echo "${{ secrets.K3S_SSH_KEY }}" > k3s.pem chmod 600 k3s.pem - - # 关键:上传仓库根目录的deploy.yaml到K3s临时目录(解决路径不存在) - scp -i k3s.pem -o StrictHostKeyChecking=no ./deploy.yaml root@${K3S_HOST}:/tmp/ - - # 执行kubectl命令(指向临时文件+补充命名空间) + # 调试:验证私钥是否正确写入 + echo "私钥文件权限:" + ls -l k3s.pem + echo "私钥头部(仅前5行):" + head -5 k3s.pem + # 测试连接(会输出服务器主机名和kubectl版本) + ssh -i k3s.pem -o StrictHostKeyChecking=no -o ConnectTimeout=10 root@${K3S_HOST} "hostname && kubectl version --client" + # 正式执行部署命令 ssh -i k3s.pem -o StrictHostKeyChecking=no root@${K3S_HOST} << CMD - kubectl apply -f /tmp/deploy.yaml - kubectl rollout restart deployment ${APP_NAME} -n default - # 可选:清理临时文件 - rm -f /tmp/deploy.yaml + kubectl apply -f /data/k3s-data/deploy.yaml + kubectl rollout restart deployment ${APP_NAME} CMD \ No newline at end of file