# Deploy Filecoin Node

### Deploy Node

{% code title="calibration.yaml" %}

```yaml
apiVersion: filecoin.kotal.io/v1alpha1
kind: Node
metadata:
  name: calibration-node
spec:
  network: calibration
```

{% endcode %}

This is a simple filecoin `Node` that joins calibration test network.

Let's deploy the node:

```bash
kubectl apply -f calibration.yaml
```

Kotal operator will notice your `calibration-node` and will create all the necessary pods, persistent volumes, services, configmaps, and secrets.

```bash
kubectl get peers
```

It will return an output similar to the following:

```bash
NAME                NETWORK        CLIENT
calibration-node    calibration    lotus
```

### Fetch Node Logs

Get the pods created for the node:

```bash
kubectl get pods
```

It will return an output similar to the following:

```bash
NAME                  READY   STATUS    RESTARTS   AGE
calibration-node-0    1/1     Running   0          5m
```

{% hint style="info" %}
If pod `STATUS` is `Pending`, most probably it's due to not enough cpu and memory, because Kotal allocates lots of cpu cores and memory for public nodes. The required node resources can be changed using `spec.resources.cpu`, `spec.resources.memory`, and `spec.resources.storage`.
{% endhint %}

Check the logs of the running node:

```bash
kubectl logs -f calibration-node-0
```

Finally you can delete the filecoin node and all its resources by

```bash
kubectl delete -f calibration.yaml
```

and kubernetes garbage collector will delete all resources created by the node controller.


---

# 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/filecoin/node.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.