-
Notifications
You must be signed in to change notification settings - Fork 128
/
values-vsphere.yaml
143 lines (106 loc) · 4.51 KB
/
values-vsphere.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
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
cloudprovider: vsphere
cloudCredentialSecretName: vsphere
# 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: {}
# specify nodepool name
name: vsphere-nodepool-1
# vSphere vm configuration parameters (used for guestinfo)
# cfgparam: []
# If you choose creation type clone a name of what you want to clone is required
# cloneFrom: ""
# Contents of cloud-config yaml file to put into the ISO user-data; Format should be:
# cloudConfig: |
# #cloud-config
# <custom cloud-config>
# vSphere cloud-init filepath or url to add to guestinfo, filepath will be read and base64 encoded before adding
# cloudinit: ""
# If you choose to clone from a content library template specify the name of the library
# contentLibrary: ""
# vSphere CPU number for docker VM
cpuCount: "2"
# 'Creation type when creating a new virtual machine. Supported values: vm, template, library, legacy'
creationType: "vm"
# vSphere custom attribute, format key/value e.g. '200=mycustom value'
# customAttribute: ["200=mycustom value"]
# vSphere datacenter for virtual machine
# datacenter: ""
# vSphere datastore for virtual machine
# datastore: ""
# vSphere datastore cluster for virtual machine
# datastoreCluster: ""
# vSphere size of disk for docker VM (in MB)
diskSize: "20480"
# vSphere folder for the docker VM. This folder must already exist in the datacenter
# folder: ""
# vSphere compute resource where the docker VM will be instantiated. This can be omitted if using a cluster with DRS
# hostsystem: ""
# vSphere size of memory for docker VM (in MB)
# memorySize: "2048"
# vSphere network where the virtual machine will be attached
# network: ""
# vSphere resource pool for docker VM
# pool: ""
# If using a non-B2D image you can specify the ssh port
sshPort: "22"
# If using a non-B2D image the uploaded keys will need chown'ed, defaults to staff e.g. docker:staff
sshUserGroup: staff
# vSphere tag id e.g. urn:xxx
# tag: ["urn:xxx"]
# 'vSphere vApp IP allocation policy. Supported values are: dhcp, fixed, transient and fixedAllocated'
# vappIpallocationpolicy: ""
# 'vSphere vApp IP protocol for this deployment. Supported values are: IPv4 and IPv6'
# vappIpprotocol: ""
# vSphere vApp properties
# vappProperty: []
# 'vSphere OVF environment transports to use for properties. Supported values are: iso and com.vmware.guestInfo'
# vappTransport: ""
# vSphere IP/hostname for vCenter
# vcenter: ""
# vSphere Port for vCenter
vcenterPort: 443