Skip to main content
Lerian Console is the unified web interface for managing Lerian products. It provides dashboards for ledger operations, account management, transaction monitoring, and plugin configuration through a single UI.

​
What the chart installs

The chart installs one web workload: a Deployment, a Service, a ConfigMap, a Secret, and a ServiceAccount. It adds an Ingress, a HorizontalPodAutoscaler, and a PodDisruptionBudget when you enable each of them. The chart bundles a MongoDB subchart and enables it by default. Console stores its own data there. Set mongodb.enabled: false to point Console at an externally managed MongoDB.

​
Prerequisites

​
Key configuration

The chart defaults point Console at a Midaz release named midaz in the midaz namespace, and at an Access Manager release named plugin-access-manager in the plugin-access-manager namespace. If you use other names, override the MIDAZ_*, PLUGIN_AUTH_*, and PLUGIN_IDENTITY_* values under configmap. Console reads Fees, Holders, and Alias Accounts from the Ledger /v2 API. The chart has no default for that address. Without it, these pages fail:
If you deploy Tracer, also set TRACER_BASE_PATH to the Tracer service address, without /v1. Set the credentials in the secrets block, or point the release at your own Secret with useExistingSecret. The chart ships NEXTAUTH_SECRET, MONGODB_PASS, and PLUGIN_AUTH_CLIENT_SECRET empty. Leave MONGODB_PASS empty with the bundled MongoDB: Console then reads the password from the MongoDB Secret. The chart puts Console in the product-console namespace, and the bundled MongoDB in the release namespace. Console reads the MongoDB Secret when both are in one namespace, so install the release in product-console. In another namespace, set mongodb.auth.rootPassword and secrets.MONGODB_PASS to the same value.

​
Public configuration values

Console reads the NEXT_PUBLIC_* values on this page when the container starts. To change one of them, set it in your values file and run helm upgrade. The chart then restarts the Console pods. The chart sets these values in its ConfigMap: The chart does not declare the keys below. Set them under extraEnvVars:

​
OCI registry

​
Installation

Read the current chart version and the application version it deploys before you install:

​
Upgrade and uninstall

Uninstalling removes the Kubernetes resources. Check the storage settings of the bundled MongoDB subchart before you uninstall, and back up the data you want to keep.

​
Resources