Vmware Cluster
Creates a new VMware cluster in a given project and location.
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.
The resource name of the VMware admin cluster hosting this user cluster.
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.
The time at which VMware user cluster was created.
VmwareDataplaneV2Config specifies configuration for Dataplane V2.
The time at which VMware user cluster was deleted.
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.
Fleet configuration for the cluster.
Load balancer configuration.
The object name of the VMware OnPremUserCluster custom resource on the associated admin cluster. This field is used to support conflicting names when enrolling existing clusters to the API. When used as a part of cluster enrollment, this field will differ from the ID in the resource name. For new clusters, this field will match the user provided cluster name and be visible in the last component of the resource name. It is not modifiable. All users should use this name to access their cluster using gkectl or kubectl and should expect to see the local name when viewing admin cluster controller logs.
The VMware user cluster network configuration.
The Anthos clusters on the VMware version for your user cluster. Defaults to the admin cluster version.
If set, there are currently changes in flight to the VMware user cluster.
ResourceStatus representing detailed cluster state.
Storage configuration.
The time at which VMware user cluster was last updated.
ValidationCheck represents the result of the preflight check job.
VmwareVCenterConfig specifies vCenter config for the user cluster. Inherited from the admin cluster.
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.