Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: TIUP 部署问题
[TiDB Usage Environment] Poc
[TiDB Version]
[Encountered Problem: Phenomenon and Impact]
When the company deploys tidb-server, grafana, and other components in containers, an error occurs.
The online solution suggests enabling container privileged mode, but since this mode allows operations on the physical machine, the container team does not approve.
How can this problem be resolved?
[Resource Configuration]
Deploy TiDB in containers using TiDB Operator.
Because there are already more than a dozen online services running, the purpose of containerizing this time is to containerize some components to save physical machine space.
How to adjust deployment variable parameters? Is it in the tiup deployment command or in the configuration file?
This is a parameter specified for the ansible deployment method, it should not be available for the tiup deployment method.
Is there any other way to modify the process supervision method when deploying with tiup? As long as it doesn’t use systemd, anything else seems fine.
I’m not an expert, but tiup seems to only manage tidb processes through systemd.
Sure, after looking up some information, it seems that besides Ansible, TiUP indeed only supports the systemd process method. Thanks a lot.
You can check out the documentation here, it might also be helpful:
Okay, got it. The current situation is that the company’s cloud platform would incur high transformation costs across multiple departments if we use the operator, and the current operation and maintenance model is also not very compatible, making it quite difficult to manage.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
|
username: Hacker_5KEgzcj2
|
username: 
|
username: 
|
username: