New wallet instance

Configure the instance through the form or YAML, then review one exact deployment plan.

Deployment readiness0/5

Wallet setup

Set the wallet identity, choose its purpose and target cluster, then pin the software it will run.

Institution nameUsed to generate the wallet instance name.PurposeWallet instance nameGenerated from institution and purpose; edit if needed.LabelsComma-separated, e.g. sandbox, customer-aUser groupsKeycloak groups that own this instance

Target cluster

Wallet identity and domain overrides

Name

generated after institution

Domain

auto after institution

Owner

saulius.prasmantas@example.com

Cluster

DomainOwner

Software and delivery

Pin component releases, choose the chart source, and define how images reach the cluster.

App images

Each component releases on its own train. Pin all; the plan records exact digests.

Wallet

Policy node

Approver Web

Own image tag; does not inherit the Wallet release.

configmap-init

Own release train (v0.x, Blockdaemon/configmap-init) — not tied to wallet versions.

Helm chart

OCI repoVersionApply runs helm with --version. Never re-resolved after approval.

helm upgrade --install … oci://iv.sepior.net/charts/mpc --version <version>

No chart version resolved yet.

Delivery method

Cluster pull. Kubernetes pulls images directly from the selected registry.

Platform check

not verified

Image platform has not been verified yet.

target · arch unknown

Image registryKubernetes pulls workload images from this registryImage pull secretoptional imagePullSecrets entry for images from the selected registry

target loadingsource loadingcatalog loading

Lifecycle

Choose how long the instance should live and how its deployment is governed.

Expiration

demo-24h

Cleanup

approval required

Review

plan first

Apply

manual approval

Setup

Step 1 of 5 · Identity, images and lifetime