Vmware
Creates a new VMware cluster in a given project and location.
Constructors
Properties
The admin cluster this VMware user cluster belongs to. This is the full resource name of the admin cluster's fleet membership. In the future, references to other resource types might be allowed if admin clusters are modeled as their own resources.
Annotations on the VMware user cluster. This field has the same restrictions as Kubernetes annotations. The total size of all keys and values combined is limited to 256k. Key can have 2 segments: prefix (optional) and name (required), separated by a slash (/). Prefix must be a DNS subdomain. Name must be 63 characters or less, begin and end with alphanumerics, with dashes (-), underscores (_), dots (.), and alphanumerics between.
AAGConfig specifies whether to spread VMware user cluster nodes across at least three physical hosts in the datacenter.
RBAC policy that will be applied and managed by the Anthos On-Prem API.
Configuration for auto repairing.
VMware user cluster control plane nodes must have either 1 or 3 replicas.
VmwareDataplaneV2Config specifies configuration for Dataplane V2.
A human readable description of this VMware user cluster.
Enable control plane V2. Default to false.
This checksum is computed by the server based on the value of other fields, and may be sent on update and delete requests to ensure the client has an up-to-date value before proceeding. Allows clients to perform consistent read-modify-writes through optimistic concurrency control.
Load balancer configuration.
The VMware user cluster network configuration.
The Anthos clusters on the VMware version for your user cluster. Defaults to the admin cluster version.
Storage configuration.
Enable VM tracking.
User provided identifier that is used as part of the resource name; This value must be up to 40 characters and follow RFC-1123 (https://tools.ietf.org/html/rfc1123) format.