Failed to Change Server Type to NodePort When Deploying TiDB on k8s

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: k8s部署tidb 修改svr type 为NodePort不成功

| username: liuis

【TiDB Environment】Testing/
【TiDB Version】v6.5.0
【Encountered Issue: Phenomenon and Impact】 After changing svr type to nodeport, it automatically restarted and reverted to cluster mode
【TiDB Operator Version】:
【K8s Version】: v1.21

image
image1380×454 133 KB

2
| username: ffeenn | Original post link

You have a small problem here. You can try creating a new svc to expose the port. If you’re not familiar with operating the cluster, I suggest you use KubeSphere. Refer to this: External Applications - Deploy TiDB Operator and TiDB Cluster - “KubeSphere v3.1 User Manual” - BookStack

3
| username: liuis | Original post link

There is no problem with deploying a separate svc to expose the service. The issue is that every time I modify its own basic-tidb svc, why does its type always change to cluster? Is there something else changing this?

4
| username: Lucien-卢西恩 | Original post link

You can check the pod logs of basic-tidb. Additionally, if it’s a production environment, it is recommended to use LB. Refer to 访问 Kubernetes 上的 TiDB 集群 | PingCAP 文档中心

5
| username: liuis | Original post link

Okay, thank you.

6
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.