bk-repo
bk-repo copied to clipboard
TencentBlueKing
蓝鲸制品库平台(BlueKing REPO)
**What would you like to be added**: 提供处理迁移失败node接口 **Why is this needed**: 方便处理失败node
**What happened**: **What you expected to happen**: **How to reproduce it (as minimally and precisely as possible)**: **Anything else we need to know?**: 由于路由没变，所以点击刷新无变化。点击查询无变化是由于查询是统合2部分的数据，从中进行筛选，无请求。 **Environment**: - bk-repo version (use `cat...
issue 1. #1760 描述 1. simple接口检索不到含有特殊字符和大写字母的包 2. simple接口返回格式不符合规范
**What happened**: **What you expected to happen**: **How to reproduce it (as minimally and precisely as possible)**: **Anything else we need to know?**: **Environment**: - bk-repo version (use `cat VERSION`...
**What happened**: **What you expected to happen**: **How to reproduce it (as minimally and precisely as possible)**: **Anything else we need to know?**: **Environment**: - bk-repo version (use `cat VERSION`...
**What happened**: **What you expected to happen**: **How to reproduce it (as minimally and precisely as possible)**: **Anything else we need to know?**: **Environment**: - bk-repo version (use `cat VERSION`...
kubectl logs bk-apigateway-operator-5655c9dc66-msx49 Defaulted container "operator" out of: operator, wait-storages (init) {"level":"info","ts":"2024-04-18 05:22:45","logger":"kube-agent-runner","caller":"runner/kube.go:107","msg":"starting manager"} {"level":"info","ts":"2024-04-18 05:22:45","logger":"etcd-resource-store","caller":"etcd/resource.go:81","msg":"Create etcd resource store","prefix":"/bk-gateway-apisix/plugin_metadata/"} {"level":"info","ts":"2024-04-18 05:22:45","logger":"etcd-resource-store","caller":"etcd/resource.go:94","msg":"etcdLocalResourceStore start full sync","prefix":"/bk-gateway-apisix/plugin_metadata/"} {"level":"info","ts":"2024-04-18 05:22:45","logger":"etcd-resource-store","caller":"etcd/resource.go:81","msg":"Create etcd resource store","prefix":"/bk-gateway-apisix/routes/"} {"level":"info","ts":"2024-04-18...
issue: 1. #1689 描述： 1. oci本地仓库支持上传多架构镜像，新增对fat manifest文件类型的处理逻辑。 2. 上传多架构镜像时，对于fat manifest会单独创建版本，并以tag作为其版本号；对于具体架构的manifest则另行创建以`sha256:xxx`格式为版本号的版本（以下称为摘要版本）。 3. 摘要版本的页面使用指引进行特殊处理（ `docker pull image:sha256:xxx`更改为`docker pull image@sha256:xxx`）（另行提交pr）。 4. `OciManifestArtifactInfo`生成fullPath的逻辑是暂时的，在后续提交pr新增OCI远程仓库对fat manifest的支持时，将对这部分逻辑进行修改。 5. 兼容原有镜像，对原本的功能没有影响。
**What would you like to be added**: **Why is this needed**:
