When using the official helm package to deploy to k8s, a buildkitsandbox access error will occur when logging in to the 6060 management port.

[JasonYHZ]

Bug Description
When using the official helm package to deploy to k8s, a buildkitsandbox access error will occur when logging in to the 6060 management port.
After actual deployment, it was found that the container already has the TAOS_FQDN environment variable set, which points to the DNS of the container itself. However, there is also an /etc/taos/taos.cfg file in which the fqdn is configured to point to buildkitsandbox. This causes the aforementioned issue. A temporary solution requires manually editing the /etc/hosts file inside the Pod to add 127.0.0.1 --- buildkitsandbox for proper login functionality.

To Reproduce
Steps to reproduce the behavior:

1. Download the official Helm package.
2. Change the version to 3.3.1.0.
3. After deployment, expose the service to access the management page on port 6060 for login.

Expected Behavior
I hope this problem will not appear again after deployment through helm.

Screenshots

Environment (please complete the following information):

• OS: official images
• TDengine Version 3.3.1.0

Additional Context
https://github.com/taosdata/TDengine-Operator/
https://docs.tdengine.com/deployment/helm/