BareMetalCluster

The admin cluster this bare metal user cluster belongs to. This is the full resource name of the admin cluster's fleet membership.

The resource name of the bare metal admin cluster managing this user cluster.

Annotations on the bare metal 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.

Required. User provided identifier that is used as part of the resource name; must conform to RFC-1034 and additionally restrict to lower-cased letters. This comes out roughly to: /^a-z+a-z0-9$/

The Anthos clusters on bare metal version for your user cluster.

Cluster operations configuration.

Control plane configuration.

The time when the bare metal user cluster was created.

The time when the bare metal user cluster was deleted. If the resource is not deleted, this must be empty

A human readable description of this bare metal user cluster.

The IP address of the bare metal user cluster's API server.

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 bare metal user cluster 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 name 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. When the local name and cluster name differ, the local name is used in the admin cluster controller logs. You use the cluster name when accessing the cluster using bmctl and kubectl.

Maintenance configuration.

Status of on-going maintenance tasks.

Immutable. The bare metal user cluster resource name.

Network configuration.

Node access related configurations.

Workload node configuration.

OS environment related configurations.

Proxy configuration.

If set, there are currently changes in flight to the bare metal user cluster.

Security related setting configuration.

The current state of the bare metal user cluster.

Detailed cluster status.

Storage configuration.

The unique identifier of the bare metal user cluster.

The time when the bare metal user cluster was last updated.

The result of the preflight check.