spec:
size: 3
This will use default version that etcd operator chooses.
spec:
size: 3
version: 3.1.1
spec:
size: 3
pod:
nodeSelector:
diskType: ssd
antiAffinity: true
spec:
size: 3
pod:
resources:
limits:
cpu: 300m
memory: 200Mi
requests:
cpu: 200m
memory: 100Mi
See example .
spec:
size: 3
version: "3.1.2"
backup:
backupIntervalInSecond: 300
maxBackups: 5
storageType: "S3"
If a cluster cluster-a
was created with backup, but deleted or failed later on,
we can recover the cluster as long as the PV still exists.
Note that delete cluster-a
Cluster resource first if it still exists.
Here's an example:
metadata:
name: "cluster-a"
spec:
size: 3
version: "3.1.2"
backup:
backupIntervalInSecond: 300
maxBackups: 5
storageType: "PersistentVolume"
pv:
volumeSizeInMB: 512
restore:
backupClusterName: "cluster-a"
storageType: "PersistentVolume"
Same as above but using "S3" as backup storage.
metadata:
name: "cluster-a"
spec:
size: 3
version: "3.1.2"
backup:
backupIntervalInSecond: 300
maxBackups: 5
storageType: "S3"
restore:
backupClusterName: "cluster-a"
storageType: "S3"
If user wants to clone a new cluster cluster-b
from an existing cluster cluster-a
,
as long as backup exists, use the following example spec:
metadata:
name: "cluster-b"
spec:
size: 3
version: "3.1.2"
backup:
backupIntervalInSecond: 300
maxBackups: 5
storageType: "PersistentVolume"
pv:
volumeSizeInMB: 512
restore:
backupClusterName: "cluster-a"
storageType: "PersistentVolume"