# Ethereum 2.0

We've extended Kubernetes with `BeaconNode` and `Validator` custom resources which can be used to deploy Ethereum 2.0 beacon nodes and validator clients from the given spec.

{% hint style="info" %}
Kotal seperates between beacon node and validator client by using different API resources `BeaconNode` and `Validator`. So you can't run a beacon node and validator client in the same process/container.
{% endhint %}

### Beacon Node

`BeaconNode` is Ethereum 2.0 beacon node -optionally- connecting to Ethereum 1 endpoint and syncing the beacon chain.

Here's an example of ConsenSys Teku beacon node `BeaconNode` syncing mainnet beacon chain, connecting to Ethereum 1 JSON RPC endpoint, enabling REST API server which is listening at port 8888:

```yaml
apiVersion: ethereum2.kotal.io/v1alpha1
kind: BeaconNode
metadata:
  name: teku-beacon-node
spec:
  network: mainnet
  client: teku
  rest: true
  restPort: 8888
  eth1Endpoints:
    - http://besu-mainnet-node:8545
```

For all the fields associated with the `BeaconNode` API resource:

```bash
kubectl explain beaconnode --api-version ethereum2.kotal.io/v1alpha1
kubectl explain beaconnode.spec --api-version ethereum2.kotal.io/v1alpha1
```

Full beacon node reference is documented [here](/reference/ethereum2.md).

### Validator Client

`Validator` is Ethereum 2.0 validator client connecting to beacon node endpoint and validating blocks using the loaded keystores.

Here's an example of ConsenSys Teku validator client connecting to beacon node endpoint, validating pyrmont blocks using 1 loaded validator keystore from its secret:

```yaml
apiVersion: ethereum2.kotal.io/v1alpha1
kind: Validator
metadata:
  name: teku-validator
spec:
  network: pyrmont
  client: teku
  beaconEndpoints:
    - http://teku-beacon-node:8888
  graffiti: Validated by Kotal
  keystores:
    - secretName: my-validator
```

For all the fields associated with the `Validator` API resource:

```bash
kubectl explain validator --api-version ethereum2.kotal.io/v1alpha1
kubectl explain validator.spec --api-version ethereum2.kotal.io/v1alpha1
kubectl explain validator.spec.keystores --api-version ethereum2.kotal.io/v1alpha1
```

Full validator client reference is documented [here](/reference/ethereum2.md).

### Multi-client Support

Kotal supports the following Ethereum 2.0 beacon node and validator clients:

* [Teku](https://docs.teku.consensys.net/en/latest/) by ConsenSys.
* [Lighthouse](https://lighthouse-book.sigmaprime.io) by Sigma Prime.
* [Prysm](https://docs.prylabs.network/docs/getting-started/) by Prysmatic Labs.
* [Nimbus](https://nimbus.guide) by Status.im.

Setting validator or beacon node client is as simple as changing the `spec.client` to the desired client.


---

# Agent Instructions: 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:

```
GET https://docs.kotal.co/tutorials/ethereum2.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.