forked from rancher/cluster-template-examples
-
Notifications
You must be signed in to change notification settings - Fork 0
/
values-harvester.yaml
71 lines (59 loc) · 2.33 KB
/
values-harvester.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
cloudprovider: harvester
cloudCredentialSecretName: harvester
# Specify nodepool options. Can add multiple node groups, specify etcd, controlplane and worker roles.
nodepools:
- etcd: true
controlplane: true
worker: true
# specify node labels
labels: {}
# specify node taints
taints: {}
# specify nodepool size
quantity: 1
# Pause node pool
# paused: false
# specify displayName
# displayName: ""
# specify rolling update mechanism
# rollingUpdate:
# The maximum number of machines that can be unavailable during the update.
# Value can be an absolute number (ex: 5) or a percentage of desired
# machines (ex: 10%).
# Absolute number is calculated from percentage by rounding down.
# This can not be 0 if MaxSurge is 0.
# Defaults to 0.
# Example: when this is set to 30%, the old MachineSet can be scaled
# down to 70% of desired machines immediately when the rolling update
# starts. Once new machines are ready, old MachineSet can be scaled
# down further, followed by scaling up the new MachineSet, ensuring
# that the total number of machines available at all times
# during the update is at least 70% of desired machines.
# maxUnavailable: "5"
# The maximum number of machines that can be scheduled above the
# desired number of machines.
# Value can be an absolute number (ex: 5) or a percentage of
# desired machines (ex: 10%).
# This can not be 0 if MaxUnavailable is 0.
# Absolute number is calculated from percentage by rounding up.
# Defaults to 1.
# Example: when this is set to 30%, the new MachineSet can be scaled
# up immediately when the rolling update starts, such that the total
# number of old and new machines do not exceed 130% of desired
# machines. Once old machines have been killed, new MachineSet can
# be scaled up further, ensuring that total number of machines running
# at any time during the update is at most 130% of desired machines.
# maxSurge: "1"
# specify machineDeployment Labels
# machineDeploymentLabels: {}
# specify machineDeployment annotations
# machineDeploymentAnnotations: {}
name: harvester-nodepool-1
diskSize: 40
diskBus: virtio
cpuCount: 4
memorySize: 8
networkName: default/network-name-1
imageName: default/image-rand
vmNamespace: default
sshUser: ubuntu