Bare Metal Admin Cluster
Creates a new bare metal admin cluster in a given project and location. The API needs to be combined with creating a bootstrap cluster to work. See: https://cloud.google.com/anthos/clusters/docs/bare-metal/latest/installing/creating-clusters/create-admin-cluster-api#prepare_bootstrap_environment Note - this resource's API doesn't support deletion. When deleted, the resource will persist on Google Cloud even though it will be deleted from Pulumi state.
Properties
Annotations on the bare metal admin 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 the bare metal admin cluster.
Cluster operations configuration.
Control plane configuration.
The time at which this bare metal admin cluster was created.
The time at which this bare metal admin cluster was deleted. If the resource is not deleted, this must be empty
A human readable description of this bare metal admin cluster.
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 cluster custom resource. 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.
Maintenance configuration.
MaintenanceStatus representing state of maintenance.
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 Admin Cluster.
Security related configuration.
ResourceStatus representing detailed cluster status.
Storage configuration.
The time at which this bare metal admin cluster was last updated.
ValidationCheck representing the result of the preflight check.