使用k8s创建tidb，根据官网提供的步骤，通过tidb-operator进行操作，前期步骤没有报异常，但是最后部署tidb的时候没有启动POD
[root@hadoop01 tidb-operator]# kubectl get pods -n tidb-cluster
No resources found in tidb-cluster namespace.
K8S的版本
[root@hadoop01 tidb-operator]# kubectl version
Client Version: version.Info{Major:“1”, Minor:“16”, GitVersion:“v1.16.9”, GitCommit:“a17149e1a189050796ced469dbd78d380f2ed5ef”, GitTreeState:“clean”, BuildDate:“2020-04-16T11:44:51Z”, GoVersion:“go1.13.9”, Compiler:“gc”, Platform:“linux/amd64”}
Server Version: version.Info{Major:“1”, Minor:“16”, GitVersion:“v1.16.9”, GitCommit:“a17149e1a189050796ced469dbd78d380f2ed5ef”, GitTreeState:“clean”, BuildDate:“2020-04-16T11:36:15Z”, GoVersion:“go1.13.9”, Compiler:“gc”, Platform:“linux/amd64”}
[root@hadoop01 tidb-operator]# kubectl get tidbclusters -n tidb-cluster basic
NAME READY PD STORAGE READY DESIRE TIKV STORAGE READY DESIRE TIDB READY DESIRE AGE
basic 5Gi 1 5Gi 1 1 14m
[root@hadoop01 tidb-operator]# kubectl describe tidbclusters -n tidb-cluster basic
Name: basic
Namespace: tidb-cluster
Labels:
Annotations:
API Version: pingcap.com/v1alpha1
Kind: TidbCluster
Metadata:
Creation Timestamp: 2021-09-01T09:40:51Z
Generation: 1
Resource Version: 25621
Self Link: /apis/pingcap.com/v1alpha1/namespaces/tidb-cluster/tidbclusters/basic
UID: 69278a39-c176-4338-b3f0-8d3d80633019
Spec:
Config Update Strategy: RollingUpdate
Discovery:
Limits:
Cpu: 0.1
Requests:
Cpu: 0.1
Enable Dynamic Configuration: true
Pd:
Base Image: pingcap/pd
Config:
Replicas: 1
Requests:
Storage: 5Gi
Storage Class Name: local-storage
Pv Reclaim Policy: Delete
Tidb:
Base Image: pingcap/tidb
Config:
Replicas: 1
Service:
Type: ClusterIP
Tikv:
Base Image: pingcap/tikv
Config:
Raftdb:
Max - Open - Files: 256
Rocksdb:
Max - Open - Files: 256
Storage:
Reserve - Space: 0MB
Replicas: 1
Requests:
Storage: 5Gi
Storage Class Name: local-storage
Timezone: UTC
Version: v5.1.1
Events:
