> For the complete documentation index, see [llms.txt](https://docs.hiero.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hiero.org/block-node-home/production-runbook/overview.md). # Overview > **Scope:** Tier 1 Block Node operators deploying to a production network (mainnet, testnet, or future Hiero networks) using the Local Full History (LFH) profile. Examples use `--profile=mainnet`; substitute the appropriate profile for your target network. Tier 2 deployment is not covered here. *** ## Who this guide is for This guide is written for: * **Council operators** deploying a Tier 1 mainnet Block Node * **Sysadmins and DevOps engineers** who own the host, Kubernetes cluster, and lifecycle * **Technical stakeholders** who need to understand the end-to-end deployment process Readers are assumed to be comfortable with Linux system administration, Kubernetes basics, and Helm. This is a production deployment guide, not a beginner walkthrough. *** ## What this guide covers A Tier 1 Block Node runs as a Helm chart inside a single-node Kubernetes cluster on operator-owned bare-metal hardware. The supported interface for installation and lifecycle management is **Solo Provisioner** (`solo-provisioner`), distributed from the [`solo-weaver`](https://github.com/hashgraph/solo-weaver) repository. | Component | Role | | ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Block Node** (`hiero-block-node`) | Ingests block streams from Consensus Nodes, maintains live state, serves block data to subscribers | | **Solo Provisioner** (`solo-provisioner`) | Installs and manages the full host stack: Kubernetes (kubeadm/kubelet, CRI-O, Cilium, MetalLB), the Block Node Helm chart via a Kubernetes Operator (CRD), and Grafana Alloy | | **Grafana Alloy** | Telemetry agent shipping Prometheus metrics and Loki logs to the operator's observability infrastructure | This guide covers: | Page | Content | | --------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | | [Prerequisites](/block-node-home/production-runbook/prerequisites.md) | Hardware, network, TLS, and pre-deployment coordination | | [Install the Block Node](/block-node-home/production-runbook/install-block-node.md) | Solo Provisioner install with production storage flags | | [Configure Alloy Telemetry](/block-node-home/production-runbook/configure-alloy-telemetry.md) | Grafana Alloy setup and remote-write configuration | | [Network Validation and Go-Live](/block-node-home/production-runbook/network-validation-go-live.md) | Validation, reset, network inclusion, and backfill | | [Steady State Operations](/block-node-home/production-runbook/steady-state-operations.md) | Health checks, upgrades, and incident reporting | | [Disaster Recovery](/block-node-home/production-runbook/disaster-recovery.md) | Four failure scenarios and resolution steps | | [Getting Help](/block-node-home/production-runbook/getting-help.md) | Support channels, community, and reference links | *** ## Responsibility model Steps across this guide are labeled with who performs them: * **\[OPERATOR]** - the council operator runs this independently * **\[HASHGRAPH]** - performed or confirmed by Hashgraph DevOps before proceeding * **\[COORDINATED]** - both parties need to be present or in communication *** ## Sensitive values Some values in this guide are intentionally not published. Placeholders indicate operator-specific or Hashgraph-provided inputs. Obtain Hashgraph-provided values through your approved coordination channel. Never commit secrets or credentials to version control. Common placeholders used in this guide: | Placeholder | Who provides it | | ----------------------------------------------- | ------------------------------------- | | `` | Operator | | `` | Operator | | `` | Hashgraph DevOps | | `` | Hashgraph DevOps | | `` | Hashgraph DevOps (via secure channel) | | `` and `_USERNAME` | Hashgraph DevOps | | `` and `_USERNAME` | Hashgraph DevOps | | `` | Hashgraph DevOps (via secure channel) | | `` | Hashgraph DevOps (via secure channel) | *** ## Related documentation * [Block Node Hardware Specifications](/block-node-home/deployment/block-node-hardware-specifications.md) * [Network Ports and Protocols](/block-node-home/configuration/network-ports-and-protocols.md) * [Block Node On-Chain Registration](/block-node-home/configuration/block-node-on-chain-registration.md) * [Operator FAQ](/block-node-home/reference/operator-faq.md) * [Solo Provisioner Quickstart](https://github.com/hashgraph/solo-weaver/blob/main/docs/quickstart.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.hiero.org/block-node-home/production-runbook/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.