在开始将自托管部署迁移到Kubernetes之前,请确认此页面上的每个先决条件。
A Ops Manager or Cloud Manager connection
ConfigMapwith the keysbaseUrl,orgId, andprojectName.An API key
Secretwith the keyspublicKeyandprivateKey.The Kubernetes Operator
ServiceAccounthasbatch/jobspermissions (create,get,list,watch, anddelete) for the dry-run connectivity Job.该项目只包含一个部署。
部署和集群要求
你需要:
An existing replica set or sharded cluster that Ops Manager or Cloud Manager manages.
已安装Kubernetes Operator 的一个或多个Kubernetes集群。对于多集群目标,在开始迁移之前预配每个集群并将其置于操作符管理之下,并确认跨集群 FQDN 解析已正常运行。
正常运行且处于目标状态的部署。
插件和 Operator RBAC
你需要:
The
kubectl mongodbplugin, at a version that matches Kubernetes Operator. Kubernetes Operator enforces this version match on every reconcile, including the dry run, through themongodb.com/migrate-tool-versionannotation.Operator Role-Based Access Control (RBAC) restricts system access based on assigned roles. Here, it includes
batch/jobspermissions (create, get, list, watch, and delete), which Kubernetes Operator requires to run the dry-run connectivity Job.
网络和证书
你需要:
Bidirectional network connectivity between the virtual machine hosts and the Kubernetes Pods. You provision this connectivity yourself. Agent-to-
mongodandmongod-to-mongodtraffic must flow in both directions across the boundary, and your drivers must reach both sides.cert-manager或等效证书颁发者(如果部署使用 TLS)。
档案和备份
你需要:
已掌握SCRAM用户密码。您无法从自动化配置中恢复它们,因为自动化配置仅存储盐、服务器密钥和存储的密钥。
开始之前进行的备份。
支持的拓扑结构和身份验证
迁移支持副本集和分片的集群。它支持 No Auth、 SCRAM-SHA-256、X.509、 LDAP和 TLS 的任意组合。当您使用LDAP时,bindMethod 必须是 simple。