pub struct HdfsClusterSpec {
pub cluster_config: HdfsClusterClusterConfig,
pub cluster_operation: Option<HdfsClusterClusterOperation>,
pub data_nodes: Option<HdfsClusterDataNodes>,
pub image: HdfsClusterImage,
pub journal_nodes: Option<HdfsClusterJournalNodes>,
pub name_nodes: Option<HdfsClusterNameNodes>,
pub object_overrides: Option<Vec<BTreeMap<String, Value>>>,
}Expand description
An HDFS cluster stacklet. This resource is managed by the Stackable operator for Apache Hadoop HDFS. Find more information on how to use it and the resources that the operator generates in the [operator documentation](https://docs.stackable.tech/home/nightly/hdfs/).
The CRD contains three roles: nameNodes, dataNodes and journalNodes.
Fields§
§cluster_config: HdfsClusterClusterConfigConfiguration that applies to all roles and role groups. This includes settings for authentication, logging and the ZooKeeper cluster to use.
cluster_operation: Option<HdfsClusterClusterOperation>[Cluster operations](https://docs.stackable.tech/home/nightly/concepts/operations/cluster_operations) properties, allow stopping the product instance as well as pausing reconciliation.
data_nodes: Option<HdfsClusterDataNodes>This struct represents a role - e.g. HDFS datanodes or Trino workers. It has a key-value-map containing
all the roleGroups that are part of this role. Additionally, there is a config, which is configurable
at the role and roleGroup level. Everything at roleGroup level is merged on top of what is configured
on role level. There is also a second form of config, which can only be configured
at role level, the roleConfig.
You can learn more about this in the
[Roles and role group concept documentation](https://docs.stackable.tech/home/nightly/concepts/roles-and-role-groups).
image: HdfsClusterImageSpecify which image to use, the easiest way is to only configure the productVersion.
You can also configure a custom image registry to pull from, as well as completely custom
images.
Consult the [Product image selection documentation](https://docs.stackable.tech/home/nightly/concepts/product_image_selection) for details.
journal_nodes: Option<HdfsClusterJournalNodes>This struct represents a role - e.g. HDFS datanodes or Trino workers. It has a key-value-map containing
all the roleGroups that are part of this role. Additionally, there is a config, which is configurable
at the role and roleGroup level. Everything at roleGroup level is merged on top of what is configured
on role level. There is also a second form of config, which can only be configured
at role level, the roleConfig.
You can learn more about this in the
[Roles and role group concept documentation](https://docs.stackable.tech/home/nightly/concepts/roles-and-role-groups).
name_nodes: Option<HdfsClusterNameNodes>This struct represents a role - e.g. HDFS datanodes or Trino workers. It has a key-value-map containing
all the roleGroups that are part of this role. Additionally, there is a config, which is configurable
at the role and roleGroup level. Everything at roleGroup level is merged on top of what is configured
on role level. There is also a second form of config, which can only be configured
at role level, the roleConfig.
You can learn more about this in the
[Roles and role group concept documentation](https://docs.stackable.tech/home/nightly/concepts/roles-and-role-groups).
object_overrides: Option<Vec<BTreeMap<String, Value>>>A list of generic Kubernetes objects, which are merged into the objects that the operator creates.
List entries are arbitrary YAML objects, which need to be valid Kubernetes objects.
Read the [Object overrides documentation](https://docs.stackable.tech/home/nightly/concepts/overrides#object-overrides) for more information.