root@flyfish71:~/tidb_v1.6# kubectl get pod -n tidb-cluster
NAME READY STATUS RESTARTS AGE
basic-discovery-6dd9cbc4b6-w8m5n 1/1 Running 0 2m41s
basic-pd-0 1/1 Running 0 2m40s
basic-tikv-0 1/1 Running 0 2m22s
root@flyfish71:~/tidb_v1.6# ls
crd.yaml tidb-cluster.yaml
root@flyfish71:~/tidb_v1.6# cat tidb-cluster.yaml
# IT IS NOT SUITABLE FOR PRODUCTION USE.
# This YAML describes a basic TiDB cluster with minimum resource requirements,
# which should be able to run in any Kubernetes cluster with storage support.
apiVersion: pingcap.com/v1alpha1
kind: TidbCluster
metadata:
name: basic
spec:
version: v8.5.2
timezone: UTC
pvReclaimPolicy: Retain
enableDynamicConfiguration: true
configUpdateStrategy: RollingUpdate
discovery: {}
helper:
image: alpine:3.16.0
pd:
baseImage: pingcap/pd
maxFailoverCount: 0
replicas: 1
# if storageClassName is not set, the default Storage Class of the Kubernetes cluster will be used
# storageClassName: local-storage
requests:
storage: "1Gi"
config: {}
tikv:
baseImage: pingcap/tikv
maxFailoverCount: 0
# If only 1 TiKV is deployed, the TiKV region leader
# cannot be transferred during upgrade, so we have
# to configure a short timeout
evictLeaderTimeout: 1m
replicas: 1
# if storageClassName is not set, the default Storage Class of the Kubernetes cluster will be used
# storageClassName: local-storage
requests:
storage: "1Gi"
config:
storage:
# In basic examples, we set this to avoid using too much storage.
reserve-space: "0MB"
rocksdb:
# In basic examples, we set this to avoid the following error in some Kubernetes clusters:
# "the maximum number of open file descriptors is too small, got 1024, expect greater or equal to 82920"
max-open-files: 256
raftdb:
max-open-files: 256
tidb:
baseImage: pingcap/tidb
maxFailoverCount: 0
replicas: 1
service:
type: ClusterIP
config: {}
kubectl get tc -o yaml
如果提 operator v1 相关的问题，首先把这个 yaml 贴上来
另外帖子可以打上 operator 的 tag
先看看TiDB Operator是否正常运行
1 个赞
应该运行不正常
根据社区规则：已多次漫骂他人
红牌警告，再骂街，封号处理
看状态，是CrashLoopBackOff、Pending 还是啥
那谁来处理我的问题
谁写的文档，让他帮我解决问题
我也不想骂人，可按照你们的文档部署不成功，为了排查问题，花费了好几天的时间，想学习你们的产品都用不了，你们就不能写文档严谨一点吗？