Cluster is the Schema for the clusters API. Deprecated: This type will be removed in one of the next releases.
5 top-level fields · last changed in Cluster API v1.9.0
APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
ClusterSpec defines the desired state of Cluster.
Cluster network configuration.
apiServerPort specifies the port the API Server should bind to. Defaults to 6443.
The network ranges from which Pod networks are allocated.
Domain name for services.
The network ranges from which service VIPs are allocated.
controlPlaneEndpoint represents the endpoint used to communicate with the control plane.
The hostname on which the API server is serving.
The port on which the API server is serving.
controlPlaneRef is an optional reference to a provider-specific resource that holds the details for provisioning the Control Plane for a Cluster.
API version of the referent.
If referring to a piece of an object instead of an entire object, this string should contain a valid JSON/Go field access statement, such as desiredState.manifest.containers[2]. For example, if the object reference is to a container within a pod, this would take on a value like: "spec.containers{name}" (where "name" refers to the name of the container that triggered the event) or if no container name is specified "spec.containers[2]" (container with index 2 in this pod). This syntax is chosen only to have some well-defined way of referencing a part of an object.
Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names
Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/
Specific resourceVersion to which this reference is made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency
UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids
infrastructureRef is a reference to a provider-specific resource that holds the details for provisioning infrastructure for a cluster in said provider.
API version of the referent.
If referring to a piece of an object instead of an entire object, this string should contain a valid JSON/Go field access statement, such as desiredState.manifest.containers[2]. For example, if the object reference is to a container within a pod, this would take on a value like: "spec.containers{name}" (where "name" refers to the name of the container that triggered the event) or if no container name is specified "spec.containers[2]" (container with index 2 in this pod). This syntax is chosen only to have some well-defined way of referencing a part of an object.
Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names
Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/
Specific resourceVersion to which this reference is made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency
UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids
paused can be used to prevent controllers from processing the Cluster and all its associated objects.
This encapsulates the topology for the cluster. NOTE: It is required to enable the ClusterTopology feature gate flag to activate managed topologies support; this feature is highly experimental, and parts of it might still be not implemented.
The name of the ClusterClass object to create the topology.
controlPlane describes the cluster control plane.
metadata is the metadata applied to the machines of the ControlPlane. At runtime this metadata is merged with the corresponding metadata from the ClusterClass. This field is supported if and only if the control plane provider template referenced in the ClusterClass is Machine based.
annotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata. They are not queryable and should be preserved when modifying objects. More info: http://kubernetes.io/docs/user-guide/annotations
Map of string keys and values that can be used to organize and categorize (scope and select) objects. May match selectors of replication controllers and services. More info: http://kubernetes.io/docs/user-guide/labels
replicas is the number of control plane nodes. If the value is nil, the ControlPlane object is created without the number of Replicas and it's assumed that the control plane controller does not implement support for this field. When specified against a control plane provider that lacks support for this field, this value will be ignored.
rolloutAfter performs a rollout of the entire cluster one component at a time, control plane first and then machine deployments.
The Kubernetes version of the cluster.
workers encapsulates the different constructs that form the worker nodes for the cluster.
machineDeployments is a list of machine deployments in the cluster.
class is the name of the MachineDeploymentClass used to create the set of worker nodes. This should match one of the deployment classes defined in the ClusterClass object mentioned in the `Cluster.Spec.Class` field.
metadata is the metadata applied to the machines of the MachineDeployment. At runtime this metadata is merged with the corresponding metadata from the ClusterClass.
annotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata. They are not queryable and should be preserved when modifying objects. More info: http://kubernetes.io/docs/user-guide/annotations
Map of string keys and values that can be used to organize and categorize (scope and select) objects. May match selectors of replication controllers and services. More info: http://kubernetes.io/docs/user-guide/labels
name is the unique identifier for this MachineDeploymentTopology. The value is used with other unique identifiers to create a MachineDeployment's Name (e.g. cluster's name, etc). In case the name is greater than the allowed maximum length, the values are hashed together.
replicas is the number of worker nodes belonging to this set. If the value is nil, the MachineDeployment is created without the number of Replicas (defaulting to zero) and it's assumed that an external entity (like cluster autoscaler) is responsible for the management of this value.
ClusterStatus defines the observed state of Cluster.
conditions defines current service state of the cluster.
Last time the condition transitioned from one status to another. This should be when the underlying condition changed. If that is not known, then using the time when the API field changed is acceptable.
A human readable message indicating details about the transition. This field may be empty.
The reason for the condition's last transition in CamelCase. The specific API may choose whether or not this field is considered a guaranteed API. This field may not be empty.
severity provides an explicit classification of Reason code, so the users or machines can immediately understand the current situation and act accordingly. The Severity field MUST be set only when Status=False.
status of the condition, one of True, False, Unknown.
type of condition in CamelCase or in foo.example.com/CamelCase. Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be useful (see .node.status.conditions), the ability to deconflict is important.
controlPlaneReady defines if the control plane is ready.
failureDomains is a slice of failure domain objects synced from the infrastructure provider.
attributes is a free form map of attributes an infrastructure provider might use or require.
controlPlane determines if this failure domain is suitable for use by control plane machines.
failureMessage indicates that there is a fatal problem reconciling the state, and will be set to a descriptive error message.
failureReason indicates that there is a fatal problem reconciling the state, and will be set to a token value suitable for programmatic interpretation.
infrastructureReady is the state of the infrastructure provider.
observedGeneration is the latest generation observed by the controller.
phase represents the current phase of cluster actuation. E.g. Pending, Running, Terminating, Failed etc.
Source: cluster.x-k8s.io_clusters.yaml
Changes to Cluster (cluster.x-k8s.io/v1alpha4) in each Cluster API version, compared to the version before it.
The description of Cluster has changed
32 properties have changed the description
Released · View Cluster in v1.9.0
The description of Cluster has changed
38 properties have changed the description
Released · View Cluster in v1.7.0
The description of Cluster has changed
Released · View Cluster in v1.4.0
1 property is no longer required
2 properties have changed the description
Released · View Cluster in v0.4.3
1 property has been added
Released · View Cluster in v0.4.1
Cluster was first seen on this version of Cluster API
Released · View Cluster in v0.4.0
No examples of Cluster yet. Contribute one on GitHub.
kubespec.dev