@@ -98,11 +98,21 @@ spec:
98
98
description.
99
99
type : string
100
100
imageName :
101
- description : ImageName describes the name of a VirtualMachineImage
102
- that is to be used as the base Operating System image of the desired
103
- VirtualMachine instances. The VirtualMachineImage resources can
104
- be introspected to discover identifying attributes that may help
105
- users to identify the desired image to use.
101
+ description : " ImageName describes the name of the image resource used
102
+ to deploy this VM. \n This field may be used to specify the name
103
+ of a VirtualMachineImage or ClusterVirtualMachineImage resource.
104
+ The resolver first checks to see if there is a VirtualMachineImage
105
+ with the specified name. If no such resource exists, the resolver
106
+ then checks to see if there is a ClusterVirtualMachineImage resource
107
+ with the specified name in the same Namespace as the VM being deployed.
108
+ \n This field may also be used to specify the display name (vSphere
109
+ name) of a VirtualMachineImage or ClusterVirtualMachineImage resource.
110
+ If the display name unambiguously resolves to a distinct VM image
111
+ (among all existing VirtualMachineImages in the VM's namespace and
112
+ all existing ClusterVirtualMachineImages), then a mutation webhook
113
+ updates this field with the VM image resource name. If the display
114
+ name resolves to multiple or no VM images, then the mutation webhook
115
+ denies the request and outputs an error message accordingly."
106
116
type : string
107
117
minHardwareVersion :
108
118
description : " MinHardwareVersion specifies the desired minimum hardware
@@ -120,29 +130,30 @@ spec:
120
130
field's value is 13, then the VM will be upgraded to hardware version
121
131
13. However, if the observed hardware version is 17 and this field's
122
132
value is 13, no change will occur. \n Several features are hardware
123
- version dependent, for example: \n * NVMe Controllers \t\t
124
- >= 14 * Dynamic Direct Path I/O devices >= 17 \n Please refer to
125
- https://kb.vmware.com/s/article/1003746 for a list of VM hardware
126
- versions. \n It is important to remember that a VM's hardware version
127
- may not be downgraded and upgrading a VM deployed from an image
128
- based on an older hardware version to a more recent one may result
129
- in unpredictable behavior. In other words, please be careful when
130
- choosing to upgrade a VM to a newer hardware version."
133
+ version dependent, for example: \n * NVMe Controllers >=
134
+ 14 * Dynamic Direct Path I/O devices >= 17 \n Please refer to https://kb.vmware.com/s/article/1003746
135
+ for a list of VM hardware versions. \n It is important to remember
136
+ that a VM's hardware version may not be downgraded and upgrading
137
+ a VM deployed from an image based on an older hardware version to
138
+ a more recent one may result in unpredictable behavior. In other
139
+ words, please be careful when choosing to upgrade a VM to a newer
140
+ hardware version."
131
141
format : int32
132
142
minimum : 13
133
143
type : integer
134
144
networkInterfaces :
135
- description : NetworkInterfaces describes a list of VirtualMachineNetworkInterfaces
145
+ description : " NetworkInterfaces describes a list of VirtualMachineNetworkInterfaces
136
146
to be configured on the VirtualMachine instance. Each of these VirtualMachineNetworkInterfaces
137
147
describes external network integration configurations that are to
138
148
be used by the VirtualMachine controller when integrating the VirtualMachine
139
- into one or more external networks.
149
+ into one or more external networks. \n The maximum number of network
150
+ interface allowed is 10 because of the limit built into vSphere."
140
151
items :
141
152
description : VirtualMachineNetworkInterface defines the properties
142
153
of a network interface to attach to a VirtualMachine instance. A
143
154
VirtualMachineNetworkInterface describes network interface configuration
144
155
that is used by the VirtualMachine controller when integrating
145
- the VirtualMachine into a VirtualNetwork. Currently, only NSX-T
156
+ the VirtualMachine into a VirtualNetwork. Currently, only NSX-T
146
157
and vSphere Distributed Switch (VDS) type network integrations
147
158
are supported using this VirtualMachineNetworkInterface structure.
148
159
properties :
@@ -162,8 +173,9 @@ spec:
162
173
type : string
163
174
networkType :
164
175
description : NetworkType describes the type of VirtualNetwork
165
- that is referenced by the NetworkName. Currently, the only
166
- supported NetworkTypes are "nsx-t" and "vsphere-distributed".
176
+ that is referenced by the NetworkName. Currently, the supported
177
+ NetworkTypes are "nsx-t", "nsx-t-subnet", "nsx-t-subnetset"
178
+ and "vsphere-distributed".
167
179
type : string
168
180
providerRef :
169
181
description : ProviderRef is reference to a network interface
@@ -189,6 +201,7 @@ spec:
189
201
- name
190
202
type : object
191
203
type : object
204
+ maxItems : 10
192
205
type : array
193
206
nextRestartTime :
194
207
description : " NextRestartTime may be used to restart the VM, in accordance
@@ -278,7 +291,10 @@ spec:
278
291
minimum : 1
279
292
type : integer
280
293
tcpSocket :
281
- description : TCPSocket specifies an action involving a TCP port.
294
+ description : " TCPSocket specifies an action involving a TCP port.
295
+ \n Deprecated: The TCPSocket action requires network connectivity
296
+ that is not supported in all environments. This field will be
297
+ removed in a later API version."
282
298
properties :
283
299
host :
284
300
description : Host is an optional host name to connect to. Host
0 commit comments