我看官方有个tikv-operator已经被archived了,还有其他方式吗
这个能只部署tikv相关组件吗,我只想用tikv的功能
???
tc.spec.tidb.replicas = 0, https://docs.pingcap.com/zh/tidb-in-kubernetes/stable/scale-a-tidb-cluster
或者纯手工部署,脱离 Operator 管控
OK,我试试看
apiVersion: apps/v1
kind: StatefulSet
metadata:
labels:
app.kubernetes.io/component: tikv
app.kubernetes.io/instance: basic
app.kubernetes.io/managed-by: tidb-operator
app.kubernetes.io/name: tidb-cluster
name: basic-tikv
namespace: tidb-cluster
ownerReferences:
- apiVersion: pingcap.com/v1alpha1
blockOwnerDeletion: true
controller: true
kind: TidbCluster
name: basic
spec:
podManagementPolicy: Parallel
replicas: 1
selector:
matchLabels:
app.kubernetes.io/component: tikv
app.kubernetes.io/instance: basic
app.kubernetes.io/managed-by: tidb-operator
app.kubernetes.io/name: tidb-cluster
serviceName: basic-tikv-peer
template:
metadata:
annotations:
prometheus.io/path: /metrics
prometheus.io/port: "20180"
prometheus.io/scrape: "true"
creationTimestamp: null
labels:
app.kubernetes.io/component: tikv
app.kubernetes.io/instance: basic
app.kubernetes.io/managed-by: tidb-operator
app.kubernetes.io/name: tidb-cluster
spec:
containers:
- command:
- /bin/sh
- /usr/local/bin/tikv_start_script.sh
env:
- name: NAMESPACE
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: metadata.namespace
- name: CLUSTER_NAME
value: basic
- name: HEADLESS_SERVICE_NAME
value: basic-tikv-peer
- name: CAPACITY
value: "0"
- name: TZ
value: UTC
image: uhub.service.ucloud.cn/pingcap/tikv:v6.5.0
imagePullPolicy: IfNotPresent
name: tikv
ports:
- containerPort: 20160
name: server
protocol: TCP
resources: {}
securityContext:
privileged: false
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:
- mountPath: /etc/podinfo
name: annotations
readOnly: true
- mountPath: /var/lib/tikv
name: tikv
- mountPath: /etc/tikv
name: config
readOnly: true
- mountPath: /usr/local/bin
name: startup-script
readOnly: true
dnsPolicy: ClusterFirst
restartPolicy: Always
schedulerName: default-scheduler
securityContext: {}
terminationGracePeriodSeconds: 30
volumes:
- downwardAPI:
defaultMode: 420
items:
- fieldRef:
apiVersion: v1
fieldPath: metadata.annotations
path: annotations
name: annotations
- configMap:
defaultMode: 420
items:
- key: config-file
path: tikv.toml
name: basic-tikv-6565313
name: config
- configMap:
defaultMode: 420
items:
- key: startup-script
path: tikv_start_script.sh
name: basic-tikv-6565313
name: startup-script
updateStrategy:
rollingUpdate:
partition: 1
type: RollingUpdate
volumeClaimTemplates:
- apiVersion: v1
kind: PersistentVolumeClaim
metadata:
creationTimestamp: null
name: tikv
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
volumeMode: Filesystem
单独部署,直接yaml帖进去就行吧
此话题已在最后回复的 60 天后被自动关闭。不再允许新回复。