基于原生k8s非标准安装接入的问题 about rainbond

[yangkaa]

如果你需要一个控制台管理多套 K8s 集群，那么还是需要使用你截图的方式，填写网关IP等相关参数配置。它会为你自动生成 helm 安装命令，并对接回这个控制台（控制台的 IP+7070 端口必须保证可以被你的集群访问到）。

其实你截图的页面可以理解为是一个快速生成 Helm 安装命令的工具，而且他不会启动 rbd-app-ui 这个pod，因为这个是 rbd-app-ui 其实就是控制台容器，你已经用 docker 运行起来了。而我发给你的文档则是完整启动一套 Rainbond，包含控制台。这也是为什么我让你删除控制台容器，否则可能会端口冲突。

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Title: Based on the problem of non-standard installation and access of native k8s

[yangkaa]

你在机器上执行，docker rm -f rainbond-allinone，移除控制台容器，然后参考这个文档直接使用 Helm 安装。

[nAnderYang]

你在机器上执行，docker rm -f rainbond-allinone，移除控制台容器，然后参考这个文档直接使用 Helm 安装。

好的我试试。请外请教下 使用docker这种方式单独创建一个rainbond的集群去管理 多个自己定义安装的k8s集群 都使用您说的文档内的方式安装吗？

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

If you need a console to manage multiple sets of K8s clusters, you still need to use the way you took screenshots to fill in the gateway IP and other related parameter configurations. It will automatically generate the helm installation command for you, and connect back to the console (the IP+7070 port of the console must be accessible by your cluster).

In fact, the page you screenshot can be understood as a tool to quickly generate Helm installation commands, and it will not start the rbd-app-ui pod, because this is rbd-app-ui, which is actually a console container, which you have already run with docker Woke up. The document I sent you is to start a complete set of Rainbond, including the console. That's why I asked you to remove the console container, otherwise there might be port conflicts.