Kubernetes Deployment with Helm Charts

Hosted option: Prefer a managed deployment? OpenScan.AI offers Explorer-as-a-Service — reach out via the contact form.

A Helm chart is available to deploy the OpenScan.AI stack (backend, frontend, and stats microservice) to a Kubernetes cluster. Baseline instructions are maintained in the OpenScanAI GitHub organization.

Troubleshooting

1. Check your values are correct — for example, if you don’t have Prometheus installed, disable it in the chart values.yaml.
2. Ingress is disabled by default, as is common practice. You will likely want to enable ingress and configure hostnames accordingly.
3. Check your .yaml files for any unneeded whitespaces — this can impact functionality.
4. Make sure env variables are declared correctly, i.e. DATABASE_URL: "X".
5. Frontend values should exist in their own root section, at the same level as the backend values (not nested within the backend root).

For example:

blockscout:
  env:
    DATABASE_URL: "X"
    ETHEREUM_JSONRPC_VARIANT: geth
    ETHEREUM_JSONRPC_HTTP_URL: "X"
    ETHEREUM_JSONRPC_TRACE_URL: "X"
  ingress:
    enabled: true
    hostname: host-name.com
frontend:
  image:
    tag: latest
  ingress:
    enabled: true

For the XDC Network, set CHAIN_ID: "50" and point the JSON RPC URLs at an XDC archive node. See ENV Variables for the full configuration surface.