forked from Altinity/clickhouse-operator
-
Notifications
You must be signed in to change notification settings - Fork 0
/
99-clickhouseupgrade-draft.yaml
116 lines (113 loc) · 3.5 KB
/
99-clickhouseupgrade-draft.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
apiVersion: "clickhouse.altinity.com/v1"
kind: "ClickHouseUpgrade"
metadata:
name: "clickhouse-installation-test"
spec:
defaults:
deployment:
zone:
matchLabels:
clickhouse.altinity.com/zone: zone1
podTemplate: clickhouse-v18.16.1
dataVolumeClaimTemplate: default
logVolumeClaimTemplate: default
# scenario: Default
configuration:
clusters:
- name: customized
# deployment:
# scenario: Default
# zone:
# matchLabels:
# clickhouse.altinity.com/zone: zone1
# podTemplate: clickhouse-v18.16.1
#
# values inherited from global .spec.deployment section
#
layout:
shards:
- index: 5
# deployment:
# scenario: Default
# zone:
# matchLabels:
# clickhouse.altinity.com/zone: zone1
# podTemplate: clickhouse-v18.16.1
#
# values inherited from .spec.configuration.clusters[3].deployment section
#
replicas:
- index: 2
tcpPort: 9000
deployment:
scenario: Default
# zone:
# matchLabels:
# clickhouse.altinity.com/zone: zone1
# podTemplate: clickhouse-v18.16.1
#
# values inherited from .spec.configuration.clusters[3].shards[2].deployment section
#
- index: 6
deployment:
scenario: NodeMonopoly # 1 pod (CH server instance) per node (zone can be a set of n nodes) -> podAntiAffinity
zone:
matchLabels:
clickhouse.altinity.com/zone: zone4
clickhouse.altinity.com/kind: ssd
podTemplate: clickhouse-v18.16.1
replicas:
- index: 2
templates:
volumeClaimTemplates:
- name: default
persistentVolumeClaim:
metadata:
name: clickhouse-data-test
# namespace: testnamespace
spec:
# 1. if storageClassName is not specified, default StorageClass
# (must be specified by cluster administrator) would be used for provisioning
# 2. if storageClassName is set to an empty string (‘’), no storage class will be used
# dynamic provisioning is disabled for this PVC. Existing, “Available”, PVs
# (that do not have a specified storageClassName) will be considered for binding to the PVC
#storageClassName: gold
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
podTemplates:
# multiple pod templates makes possible to update version smoothly
# pod template for ClickHouse v18.16.1
- name: clickhouse-v18.16.1
# volumes: are missing
containers:
- name: clickhouse
image: yandex/clickhouse-server:18.16.1
volumeMounts:
- name: clickhouse-data-test
mountPath: /var/lib/clickhouse
resources:
requests:
memory: "64Mi"
cpu: "100m"
limits:
memory: "64Mi"
cpu: "100m"
# pod template for ClickHouse v18.16.2
- name: clickhouse-v18.16.2
# volumes: are missing
containers:
- name: clickhouse
image: yandex/clickhouse-server:18.16.2
volumeMounts:
- name: clickhouse-data-test
mountPath: /var/lib/clickhouse
resources:
requests:
memory: "64Mi"
cpu: "100m"
limits:
memory: "64Mi"
cpu: "100m"