【 TiDB 使用环境】生产环境 /测试/ Poc
【 TiDB 版本】
【复现路径】做过哪些操作出现的问题
【遇到的问题：问题现象及影响】
【资源配置】
【附件：截图/日志/监控】
tidb-controller-manager-65b7c5756c-bjkqq 的日志报错如下：
I0325 12:35:02.594685 1 tidbcluster_control.go:71] TidbCluster: [tidb-cluster/basic] updated successfully
I0325 12:35:02.594735 1 tidb_cluster_controller.go:131] TidbCluster: tidb-cluster/basic, still need sync: TidbCluster: [tidb-cluster/basic], waiting for PD cluster running, requeuing
E0325 12:35:07.708892 1 pd_member_manager.go:205] failed to sync TidbCluster: [tidb-cluster/basic]'s status, error: Get "http://basic-pd.tidb-cluster:2379/pd/api/v1/health": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
I0325 12:35:07.736119 1 tidb_cluster_controller.go:131] TidbCluster: tidb-cluster/basic, still need sync: TidbCluster: [tidb-cluster/basic], waiting for PD cluster running, requeuing
E0325 12:35:12.877920 1 pd_member_manager.go:205] failed to sync TidbCluster: [tidb-cluster/basic]'s status, error: Get "http://basic-pd.tidb-cluster:2379/pd/api/v1/health": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
I0325 12:35:12.921957 1 tidbcluster_control.go:71] TidbCluster: [tidb-cluster/basic] updated successfully
I0325 12:35:12.922015 1 tidb_cluster_controller.go:131] TidbCluster: tidb-cluster/basic, still need sync: TidbCluster: [tidb-cluster/basic], waiting for PD cluster running, requeuing
E0325 12:35:18.047214 1 pd_member_manager.go:205] failed to sync TidbCluster: [tidb-cluster/basic]'s status, error: Get "http://basic-pd.tidb-cluster:2379/pd/api/v1/health": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
I0325 12:35:18.069235 1 tidb_cluster_controller.go:131] TidbCluster: tidb-cluster/basic, still need sync: TidbCluster: [tidb-cluster/basic], waiting for PD cluster running, requeuing
E0325 12:35:41.882132 1 pd_member_manager.go:205] failed to sync TidbCluster: [tidb-cluster/basic]'s status, error: Get "http://basic-pd.tidb-cluster:2379/pd/api/v1/health": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
I0325 12:35:41.915237 1 tidb_cluster_controller.go:131] TidbCluster: tidb-cluster/basic, still need sync: TidbCluster: [tidb-cluster/basic], waiting for PD cluster running, requeuing
[root@node01 v1.4.0]# k logs -n tidb-admin tidb-controller-manager-65b7c5756c-bjkqq```那个帖子我看了，他最终解决方案是重新安装了网络插件，因为它的两个网络插件一直在pending，而我的网络插件是正常运行的：
[root@node01 kube-prometheus]# k get po -n kube-system
NAME READY STATUS RESTARTS AGE
calico-kube-controllers-66686fdb54-2ccg6 1/1 Running 2 (6h55m ago) 6h55m
calico-node-4dfhd 1/1 Running 0 6h55m
calico-node-6v8wm 1/1 Running 0 6h55m
calico-node-rw54s 1/1 Running 3 (14m ago) 6h47m
calico-typha-67c6dc57d6-ctph8 1/1 Running 2 (14m ago) 3h2m
calico-typha-67c6dc57d6-f4q6k 1/1 Running 0 3h11m
calico-typha-67c6dc57d6-j4mmv 1/1 Running 0 6h55m
coredns-7d89d9b6b8-7w9t9 1/1 Running 0 80m
coredns-7d89d9b6b8-pdz27 1/1 Running 0 81m
etcd-node01 1/1 Running 0 6h56m
etcd-node02 1/1 Running 0 6h57m
但是我的端口 2379 被 k8s的etcd服务占用了，不知道是不是这个原因导致的？ 如果是请问我怎么配置pd的端口阿？搜了好久搜不到
默认组件 pod 应该使用内部 ip，不与 node port 冲突，只能调整下 cni
Operator 暂不支持调整组件端口，目前是写死在代码里的 https://github.com/search?q=2379+repo%3Apingcap%2Ftidb-operator+-path%3A*_test.go&type=code
那请问大佬可以指导一下调CNI的思路吗？