diff --git a/docs/cloud-rollup/1-digital-ocean.mdx b/docs/cloud-rollup/1-digital-ocean.mdx
new file mode 100644
index 0000000..4b511eb
--- /dev/null
+++ b/docs/cloud-rollup/1-digital-ocean.mdx
@@ -0,0 +1,329 @@
+---
+sidebar_position: 1
+---
+
+# Digital Ocean
+
+This guide will walk you through deploying a rollup full node on
+a Kubernetes cluster on Digital Ocean which uses the Astria shared sequencer network.
+
+## Local Dependencies
+
+### Install the latest [astria cli](https://github.com/astriaorg/astria/releases/tag/cli-v0.2.0)
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+
+
+
+ curl -L https://github.com/astriaorg/astria/releases/download/cli-v0.2.0/astria-cli-aarch64-apple-darwin.tar.gz > astria-cli.tar.gz
+ tar -xvzf astria-cli.tar.gz
+
+
+
+
+ curl -L https://github.com/astriaorg/astria/releases/download/cli-v0.2.0/astria-cli-x86_64-apple-darwin.tar.gz > astria-cli.tar.gz
+ tar -xvzf astria-cli.tar.gz
+
+
+
+
+ curl -L https://github.com/astriaorg/astria/releases/download/cli-v0.2.0/astria-cli-x86_64-unknown-linux-gnu.tar.gz > astria-cli.tar.gz
+ tar -xvzf astria-cli.tar.gz
+
+
+
+
+ cargo install astria-cli --git=https://github.com/astriaorg/astria --tag=cli-v2 --locked
+
+
+
+
+### You'll also need to install the following tools
+
+- kubectl -
+- helm -
+
+## Dusknet Endpoints
+
+The endpoints for the remote shared sequencer are:
+
+| NAME | HOSTS | ADDRESS |
+|-----|-----|-----|
+| Sequencer RPC | rpc.sequencer.dusk-2.devnet.astria.org | 34.111.73.187 |
+| Sequencer Faucet | faucet.sequencer.dusk-2.devnet.astria.org | 34.36.8.102 |
+
+## Create a New Cluster
+
+This guide assumes you're using Digital Ocean's Kubernetes (K8s) service.
+
+Install and configure `doctl`:
+
+Follow the instructions in Digital Ocean's [Quick Start Guide](https://docs.digitalocean.com/products/kubernetes/getting-started/)
+to create a new cluster in the region of your choosing.
+
+## Configure `kubectl` with `doctl`
+
+Once your k8s cluster is created configure `kubectl`.
+
+![doctl screenshot](assets/do-setup.png)
+
+## Deploy Ingress Nginx Controller
+
+We use the Nginx Ingress Controller, documentation can be found [here](https://kubernetes.github.io/ingress-nginx/deploy/#digital-ocean/)
+
+To install it run:
+
+```bash
+kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.8.2/deploy/static/provider/do/deploy.yaml
+```
+
+This will create several Kubernetes (k8s) resources and a Digital Ocean loadbalancer.
+
+## Verify Loadbalancer with external IP
+
+You should see a new loadbalancer being created in the Digital Ocean console:
+
+
+You can also check that your Digital Ocean load balancer was created with:
+
+```bash
+kubectl get svc -n ingress-nginx
+```
+
+It may take a few minutes for the `EXTERNAL-IP` field to be populated,
+you should eventually see something like this:
+
+```bash
+NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
+ingress-nginx-controller LoadBalancer 10.245.63.28 161.35.240.50 80:32656/TCP,443:30158/TCP 44h
+ingress-nginx-controller-admission ClusterIP 10.245.106.99 443/TCP 44h
+```
+
+## Create an `A` Record
+
+:::tip
+You must configure a DNS record because our ingress configuration uses name
+based virtual routing.
+
+More info can be found [here](https://kubernetes.io/docs/concepts/services-networking/ingress/#name-based-virtual-hosting)
+:::
+
+How you create an `A` record will depend on where you manage your domain.
+
+An example for Google domains can be seen here:
+
+Create a wildcard record `*` pointing to the `EXTERNAL-IP` of your `ingress-nginx-controller`:
+
+![a record screenshot](assets/a-record.png)
+
+## Create your Rollup Genesis Account(s)
+
+:::danger
+__NEVER__ use a private key you use on a live network.
+:::
+
+Specify the accounts which will be funded at the genesis block of your EVM rollup.
+
+You can create an account using:
+
+```bash
+cast w new
+```
+
+```bash
+Successfully created new keypair.
+Address: 0xfFe9...5f8b #
+Private key: 0x332e...a8fb #
+```
+
+Export the genesis private key,
+this will be used by the faucet included with the rollup:
+
+```bash
+export ROLLUP_FAUCET_PRIV_KEY=
+```
+
+Export the genesis address alongside with your desired initial balance in Wei.
+We recommend using a value of `100000000000000000000` or larger:
+
+```bash
+export ROLLUP_GENESIS_ACCOUNTS=:
+```
+
+You can specify multiple accounts to be funded at genesis as
+ comma deliminated tuples of `:`
+
+```bash
+export ROLLUP_GENESIS_ACCOUNTS=:,:
+```
+
+## Create Rollup Config
+
+Create the configuration manifest for your rollup.
+
+Replace the tags in the commands and env vars below, as follows:
+
+| Var Name | Var Type | Description |
+|-----|-----|-----|
+| `` | String | The name of your rollup. This must be alphanumeric, `-` is allowed, this will be included in URLs|
+| `` | u64 | The id of your network. Pick a > 6 digit number (eg. `123456`) |
+| `` | String | The chosen hostname for your network (eg. `astria.org`) |
+
+You can use environment variables to set the configuration for the rollup
+config creation. Replace all the `<>` tags with their corresponding values.
+
+```bash
+export ROLLUP_NAME=
+export ROLLUP_NETWORK_ID=
+export ROLLUP_HOSTNAME=
+```
+
+Run the config create command:
+
+```sh
+astria-cli rollup config create
+```
+
+Export the config file name as an env vars:
+
+```bash
+export ROLLUP_CONF_FILE=$ROLLUP_NAME-rollup-conf.yaml
+```
+
+Verify the config
+
+```bash
+cat $ROLLUP_CONF_FILE
+```
+
+```bash
+global:
+ namespace: astria-dev-cluster
+ useTTY: false
+ logLevel: debug
+config:
+ rollup:
+ name:
+ chainId: -chain
+ networkId: ''
+ genesisAccounts:
+ - address:
+ balance: ''
+ sequencer:
+ initialBlockHeight:
+ websocket: wss://rpc.sequencer.dusk-2.devnet.astria.org/websocket
+ rpc: https://rpc.sequencer.dusk-2.devnet.astria.org
+ingress:
+ hostname:
+celestia-node:
+ config:
+ labelPrefix:
+```
+
+## Create new sequencer account
+
+Create an account on the Astria shared sequencer network
+ for your rollup to submit transactions.
+
+```bash
+astria-cli sequencer account create
+```
+
+```bash
+Create Sequencer Account
+
+Private Key: "5562...1622" #
+Public Key: "ec20...f613" #
+Address: "8a2f...5f68" #
+```
+
+Export your sequencer private key and address as environment variables:
+
+```bash
+export SEQUENCER_PRIV_KEY=5562...1622
+export SEQUENCER_ACCOUNT_ADDRESS=8a2f...5f68
+```
+
+## Fund your Sequencer Account
+
+Navigate to
+to view the sequencer faucet.
+
+Enter your `` into the text box
+ to send funds to your account:
+
+![Sequencer Faucet](assets/sequencer-faucet.png)
+
+Verify your account received the funds
+
+```bash
+astria-cli sequencer account balance $SEQUENCER_ACCOUNT_ADDRESS
+```
+
+## Deploy the Rollup Node
+
+Use the `astria-cli` to deploy the rollup node
+
+```bash
+astria-cli rollup deployment create \
+ --config $ROLLUP_CONF_FILE \
+ --faucet-private-key $ROLLUP_FAUCET_PRIV_KEY \
+ --sequencer-private-key $SEQUENCER_PRIV_KEY
+```
+
+## Watch for rollup startup
+
+You can watch for the Kubernetes pods of the rollup to start with:
+
+```bash
+kubectl get pods -n astria-dev-cluster -w
+```
+
+```bash
+NAME READY STATUS RESTARTS AGE
+-blockscout-647745c66d-vz4ks 6/6 Running 1 (56s ago) 72s
+-celestia-node-light-mocha-4-0 2/2 Running 1 (56s ago) 72s
+-faucet-68667bd895-pwqmz 1/1 Running 0 72s
+-geth-755cb8dd97-k5xp8 3/3 Running 0 72s
+```
+
+## Your Rollup Endpoints
+
+Your rollup will automatically be configured with
+several public endpoints using the DNS you configured:
+
+| Utility | URL |
+|-----|-----|
+| Block Explorer | ../ |
+| Faucet | ../ |
+| RPC | ../ |
+
+## Interact with your Rollup
+
+```bash
+export ETH_RPC_URL=http://executor.$ROLLUP_NAME.$ROLLUP_HOSTNAME/
+```
+
+```bash
+cast block 0
+```
+
+Use an address of your choice.
+
+```bash
+export REC_ADDR=
+```
+
+```bash
+cast balance $REC_ADDR
+```
+
+```bash
+cast send $REC_ADDR --value 10000000000000000000 --private-key $ROLLUP_FAUCET_PRIV_KEY
+```
+
+```bash
+cast balance $REC_ADDR
+```
diff --git a/docs/cloud-rollup/_category_.json b/docs/cloud-rollup/_category_.json
new file mode 100644
index 0000000..b2fec37
--- /dev/null
+++ b/docs/cloud-rollup/_category_.json
@@ -0,0 +1,8 @@
+{
+ "label": "Deploy a Cloud Rollup",
+ "position": 3,
+ "link": {
+ "type": "generated-index",
+ "description": "To deploy a rollup to a cloud provider of your choice, select one of the guides below."
+ }
+}
diff --git a/docs/dusknet/assets/a-record.png b/docs/cloud-rollup/assets/a-record.png
similarity index 100%
rename from docs/dusknet/assets/a-record.png
rename to docs/cloud-rollup/assets/a-record.png
diff --git a/docs/dusknet/assets/cname-record-example.png b/docs/cloud-rollup/assets/cname-record-example.png
similarity index 100%
rename from docs/dusknet/assets/cname-record-example.png
rename to docs/cloud-rollup/assets/cname-record-example.png
diff --git a/docs/cloud-rollup/assets/do-setup.png b/docs/cloud-rollup/assets/do-setup.png
new file mode 100644
index 0000000..0874855
Binary files /dev/null and b/docs/cloud-rollup/assets/do-setup.png differ
diff --git a/docs/dusknet/assets/doctl-screenshot.png b/docs/cloud-rollup/assets/doctl-screenshot.png
similarity index 100%
rename from docs/dusknet/assets/doctl-screenshot.png
rename to docs/cloud-rollup/assets/doctl-screenshot.png
diff --git a/docs/cloud-rollup/assets/sequencer-faucet.png b/docs/cloud-rollup/assets/sequencer-faucet.png
new file mode 100644
index 0000000..732c627
Binary files /dev/null and b/docs/cloud-rollup/assets/sequencer-faucet.png differ
diff --git a/docs/dev-cluster/1-overview.md b/docs/dev-cluster/1-overview.md
deleted file mode 100644
index d663653..0000000
--- a/docs/dev-cluster/1-overview.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-sidebar_position: 1
----
-
-# Dev-Cluster Overview
-
-:::tip
-To deploy your own rollup on the Astria Dusknet devnet, check out the
-[instructions here](/docs/dusknet/overview/)!
-:::
-
-Astria's Shared Sequencer Network allows multiple rollups to share a single
-decentralized network of sequencers that’s permissionless to join. This shared
-sequencer network provides out-of-the-box censorship resistance, fast block
-confirmations, and atomic cross-rollup inclusion guarantees.
-
-The Astria [dev-cluster](https://github.com/astriaorg/dev-cluster) is the
-collective stack of all of Astria's components packaged together using
-Kubernetes. While we generally refer to Astria as the network of shared
-sequencers, we provide several other components to make it simpler to integrate
-with the shared sequencer network. The dev-cluster is provided to make
-developing and testing the Astria network, as well as integrations with Astria,
-as simple as possible.
-
-:::tip
-The primary use of the dev-cluster is running the full stack completely locally.
-There are elements of it that are used for running a local rollup that connects
-to the remote dev-net, but those will be [discussed in another
-section](/docs/dusknet/local-rollup-deployment/).
-:::
-
-See the [dev-cluster repo here.](https://github.com/astriaorg/dev-cluster)
-
-## Running the Dev Cluster Locally
-
-### Installation
-
-You will need to pull both the
-[dev-cluster](https://github.com/astriaorg/dev-cluster) and
-[astria-web3](https://github.com/astriaorg/astria-web3) repos from our github.
-
-Install the necessary dependencies and tools listed for each repo:
-
-* docker -
-* kubectl -
-* helm -
-* kind -
-* just -
-
-For contract deployment:
-
-* Forge (part of Foundry) -
-
-### Deployment
-
-:::tip
-Make sure that Docker is running before deploying with `just`.
-:::
-
-To deploy the Astria Sequencer and a local DA, open a terminal in the
-dev-cluster directory and run the commands:
-
-```bash
-# Deploys ingress + Sequencer + local DA
-just deploy-astria-local
-```
-
-This may take a minute or two if this the first time you are deploying as quite
-a few containers need to be downloaded. Once the command completes, all elements
-of the dev-cluster will be up and running. This does not run a rollup, block
-explorer, or faucet.
-
-You can now deploy a rollup.
diff --git a/docs/dev-cluster/2-deploy-a-local-rollup.md b/docs/dev-cluster/2-deploy-a-local-rollup.md
deleted file mode 100644
index 5232fc6..0000000
--- a/docs/dev-cluster/2-deploy-a-local-rollup.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-sidebar_position: 2
----
-
-# Running a Local Rollup
-
-:::tip
-To deploy your own rollup on the Astria Dusknet devnet, check out the
-[instructions here](/docs/dusknet/overview/)!
-:::
-
-## Faucet, Block Explorer, and Test Data
-
-With the dev-cluster running, you can then deploy a rollup, block explorer, and
-faucet by running the following command in the terminal withing the dev-cluster:
-
-```sh
-just deploy-rollup
-```
-
-This `just` command launches a local rollup, block explorer, and faucet using
-the default in
-[helm/rollup/values.yaml](https://github.com/astriaorg/dev-cluster/blob/main/helm/rollup/values.yaml)
-in the `config.rollup` definition.
-
-For reference, these are:
-- Rollup name: `astria`
-- Network Id: `912559`
-
-This will also take a moment as the rollup node, block explorer, and faucet spin
-up. You can check the progress of the deployment with the following command:
-
-```bash
-kubectl get deployments --all-namespaces
-```
-
-Or you can run:
-
-```bash
-just wait-for-rollup
-```
-
-Once deployed, you can view the block explorer and faucet by opening a couple
-new windows in your browser and going to to the following urls.
-
-For the block explorer:
-
-```txt
-http://blockscout.astria.localdev.me/
-```
-
-For the faucet:
-
-```txt
-http://faucet.astria.localdev.me/
-```
-
-You can copy and paste a wallet address on the faucet page and give yourself 1
-RIA.
-
-To test out the block explorer, open a terminal in the [astria-web3
-repo](https://github.com/astriaorg/astria-web3/tree/main) you downloaded earlier
-and navigate to the `packages/evm-test-data/` and run the following command:
-
-```sh
-just generate-transactions
-```
-
-This command uses the default rollup name and network id (see above), and will
-submit commands to the newly deployed default rollup.
-
-You can now go back to your browser and pull up the block explorer and you will
-now see blocks with transactions getting created in real time.
diff --git a/docs/dev-cluster/3-run-multiple-rollups-locally.md b/docs/dev-cluster/3-run-multiple-rollups-locally.md
deleted file mode 100644
index 3546b53..0000000
--- a/docs/dev-cluster/3-run-multiple-rollups-locally.md
+++ /dev/null
@@ -1,115 +0,0 @@
----
-sidebar_position: 3
----
-
-# Run Multiple Rollups Locally
-
-:::tip
-To deploy your own rollup on the Astria Dusknet devnet, check out the
-[instructions here](/docs/dusknet/overview/)!
-:::
-
-At Astria we believe strongly that deploying a rollup should be as easy as
-deploying a smart contract. The dev-cluster shows this is indeed possible.
-
-Navigate back to the [dev-cluster](https://github.com/astriaorg/dev-cluster)
-repo in your terminal and run the following command with your own rollup name
-and network id:
-
-:::warning
-
-**NOTE:** The default rollup name and network id are `astria` and `912559`. When
-deploying your second rollup you _**must**_ use a different name and number.
-
-:::
-
-```sh
-just deploy-rollup
-```
-
-As before, it will take a moment for everything to spin up, but in the meantime
-keep the the rollup name and network id handy and navigate back to your browser
-and open a new window with the following url, replacing `rollup_name` with the
-name you just used to deploy your new rollup:
-
-```txt
-http://blockscout..localdev.me/
-```
-
-Once everything has spin up you will see a new block explorer for your new rollup.
-
-You can now deploy transaction to that rollup independently.In the
-`astria-web3/packages/evm-test-data` directory open a new terminal and run the
-following:
-
-```sh
-just generate-transactions
-```
-
-As before, this command will deploy test transaction data to your new rollup.
-You can also go back to your original terminal window for the test data
-deployment on the default rollup and rerun the `just generate-transactions`
-command. If you switch back and forth between the default block explorer window
-and your new rollup window, you will see transactions showing up on each rollup
-independently!
-
-To navigate to the new Block Explorer and Faucet from the additional rollup,
-take the rollup name that you used and replace `` in the urls
-below:
-
-```txt
-http://blockscout..localdev.me/
-http://faucet..localdev.me/
-```
-
-The only limitations to running numerous rollups are the following:
-- Can your hardware handle it
-- There are no rollup name and network id clashes
-
-### What's Going on Under the Hood?
-
-One last thing to mention is what is actually happening when you deploy a new
-rollup in the dev-cluster. When you you deploy a new rollup the only new
-containers that are getting spun up in the cluster are a new rollup node, a
-conductor, block explorer, and faucet. Only one instance of the shared sequencer
-and the DA layer remain running and the transactions from all the rollups are
-collectively getting run though those networks.
-
-![Multiple Rollups](assests/multiple-rollups.png)
-
-You can also use `kubectl` to see that this is the case.
-
-When running only the default rollup:
-
-```bash
-dev-cluster % kubectl get deployments --all-namespaces
-NAMESPACE NAME READY UP-TO-DATE AVAILABLE AGE
-astria-dev-cluster astria-blockscout 1/1 1 1 37s
-astria-dev-cluster astria-faucet 1/1 1 1 37s
-astria-dev-cluster astria-geth 1/1 1 1 37s
-astria-dev-cluster celestia-local 1/1 1 1 94m
-astria-dev-cluster sequencer 1/1 1 1 94m
-ingress-nginx ingress-nginx-controller 1/1 1 1 94m
-kube-system calico-kube-controllers 1/1 1 1 95m
-kube-system coredns 2/2 2 2 95m
-local-path-storage local-path-provisioner 1/1 1 1 95m
-```
-
-After deploying the second rollup:
-
-```bash
-dev-cluster % kubectl get deployments --all-namespaces
-NAMESPACE NAME READY UP-TO-DATE AVAILABLE AGE
-astria-dev-cluster anotherrollup-blockscout 1/1 1 1 114s
-astria-dev-cluster anotherrollup-faucet 1/1 1 1 114s
-astria-dev-cluster anotherrollup-geth 1/1 1 1 114s
-astria-dev-cluster astria-blockscout 1/1 1 1 2m13s
-astria-dev-cluster astria-faucet 1/1 1 1 2m13s
-astria-dev-cluster astria-geth 1/1 1 1 2m13s
-astria-dev-cluster celestia-local 1/1 1 1 95m
-astria-dev-cluster sequencer 1/1 1 1 95m
-ingress-nginx ingress-nginx-controller 1/1 1 1 96m
-kube-system calico-kube-controllers 1/1 1 1 97m
-kube-system coredns 2/2 2 2 97m
-local-path-storage local-path-provisioner 1/1 1 1 97m
-```
diff --git a/docs/dev-cluster/4-shutdown.md b/docs/dev-cluster/4-shutdown.md
deleted file mode 100644
index fdf2f6e..0000000
--- a/docs/dev-cluster/4-shutdown.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-sidebar_position: 4
----
-
-# Shutting Down the Cluster
-
-:::tip
-To deploy your own rollup on the Astria Dusknet devnet, check out the
-[instructions here](/docs/dusknet/overview/)!
-:::
-
-## Deleting Specific Rollups
-
-To delete a specific rollup deployment, you can use the following command:
-
-```bash
-just delete-rollup
-```
-
-This will remove the rollup, its block explorer, and faucet, but keep the rest
-of the cluster running.
-
-## Shutting Down the Whole Cluster
-
-If you just want to shut everything down, you can run:
-
-```bash
-just clean
-```
-
-To delete all the data that may have also been created during your testing, you
-can then run:
-
-```bash
-just clean-persisted-data
-```
-
-Which will delete all the local data created.
diff --git a/docs/dev-cluster/_category_.json b/docs/dev-cluster/_category_.json
deleted file mode 100644
index 228b217..0000000
--- a/docs/dev-cluster/_category_.json
+++ /dev/null
@@ -1,8 +0,0 @@
-{
- "label": "Local Dev Cluster",
- "position": 3,
- "link": {
- "type": "doc",
- "id": "dev-cluster/overview"
- }
-}
diff --git a/docs/dev-cluster/assests/multiple-rollups.png b/docs/dev-cluster/assests/multiple-rollups.png
deleted file mode 100644
index da0c7b2..0000000
Binary files a/docs/dev-cluster/assests/multiple-rollups.png and /dev/null differ
diff --git a/docs/dusknet/cloud-rollup-deployment/5-faq-debugging.md b/docs/dusk-faq/1-information.md
similarity index 53%
rename from docs/dusknet/cloud-rollup-deployment/5-faq-debugging.md
rename to docs/dusk-faq/1-information.md
index dd5e159..616ea62 100644
--- a/docs/dusknet/cloud-rollup-deployment/5-faq-debugging.md
+++ b/docs/dusk-faq/1-information.md
@@ -16,21 +16,42 @@ Endpoints for the remote cluster are the following:
| Sequencer RPC | rpc.sequencer.dusk-2.devnet.astria.org | 34.111.73.187 |
| Sequencer Faucet | faucet.sequencer.dusk-2.devnet.astria.org | 34.36.8.102 |
+## Software Versions
+
+The latest Devnet (dusk-2) runs the following software versions:
+- [conductor v0.11.0](https://github.com/astriaorg/astria/releases/tag/v0.11.0--conductor)
+- [composer v0.3.0](https://github.com/astriaorg/astria/releases/tag/v0.3.0--composer)
+- [sequencer-relayer v0.9.0](https://github.com/astriaorg/astria/releases/tag/v0.9.0--sequencer-relayer)
+- [sequencer v0.7.0](https://github.com/astriaorg/astria/releases/tag/v0.7.0--sequencer)
+
## Manually Fetch Sequencer Block Height
-### Install the `astria-cli`
+### Install the latest [astria cli](https://github.com/astriaorg/astria/releases/tag/cli-v0.2.0)
+
+#### ARM Mac
+
+```bash
+curl -L https://github.com/astriaorg/astria/releases/download/cli-v0.2.0/astria-cli-aarch64-apple-darwin.tar.gz > astria-cli.tar.gz
+tar -xvzf astria-cli.tar.gz
+```
-Pull the [Astria repo](https://github.com/astriaorg/astria) and install the `astria-cli`
+#### x86_64 Linux
```bash
-git clone git@github.com:astriaorg/astria.git
-cd astria
-just install-cli
+curl -L https://github.com/astriaorg/astria/releases/download/cli-v0.2.0/astria-cli-x86_64-unknown-linux-gnu.tar.gz > astria-cli.tar.gz
+tar -xvzf astria-cli.tar.gz
+```
+
+#### From Source
+
+```bash
+cargo install astria-cli --git=https://github.com/astriaorg/astria --tag=cli-v2 --locked
```
### Sequencer Block Height
-The initial sequencer block height is automatically fetched and set if not specified when creating the config.
+The initial sequencer block height is automatically fetched and set
+(if not manually specified) when creating the rollup config.
You can manually retrieve it with the `astria-cli`:
@@ -39,7 +60,8 @@ astria-cli sequencer blockheight get \
--sequencer-url https://rpc.sequencer.dusk-2.devnet.astria.org/
```
-If you need to set this to a different value you can set it as an an environment variable:
+If you need to set this to a different value
+you can set it as an an environment variable:
```bash
export ROLLUP_SEQUENCER_INITIAL_BLOCK_HEIGHT=
@@ -51,25 +73,10 @@ command below:
```bash
--sequencer.initial-block-height
```
-## Debug Ingress
-If you would like to view the ingress logs you can use the following:
+## Loadbalancer Information
-```bash
-kubectl get po -n ingress-nginx
-# get the name of one of the pods
-export INGRESS_POD_1=ingress-nginx-controller-6d6559598-ll8gv
-# view the logs
-kubectl logs $INGRESS_POD_1 -n ingress-nginx
-```
-
-## Verify Your Loadbalancer
-
-If you want to verify your loadbalancer with an external IP you can do the
-following.
-
-After you have deployed your ingress controller with `kubectl apply`, run the
-following command and then `curl` the external IP:
+You can retrieve the kubernetes service for your loadbalancer with
```bash
kubectl get svc -n ingress-nginx
@@ -81,15 +88,15 @@ ingress-nginx-controller LoadBalancer 34.118.228.98 34.42.184.20
ingress-nginx-controller-admission ClusterIP 34.118.229.71 443/TCP 57s
```
-:::note
-If you are using AWS you will be given a URL instead of an IP.
-:::
+You can check that the loadbalancer is working by making a `curl` request
```bash
# use the EXTERNAL-IP from the result above
curl 34.42.184.206
```
+This should return the nginx 404 page
+
```html
404 Not Found
@@ -99,3 +106,11 @@ curl 34.42.184.206