accounts object of values.yaml defines Tezos accounts used in the chart.
By default no account is configured:
accounts is a map where keys are account aliases and values are maps of
key field can be set to a public or private key. For a bootstrap baker,
it must be set to a private key. The key type will be recognized automatically,
and the pod will fail if the key type is unexpected.
protocols fields overrides the top-level
protocols field described
below and has the same syntax. This allows to set specific per-block votes per
operations_pool field instructs the baker to target a url for external
mempool queries when baking a block. This is useful to run a Flashbake-capable baker.
The entry is passed to baker binaries using the
- Public chains: Accounts do not get
- Non-public chains: If you don't specify accounts needed by nodes, they can
be created deterministically via the above setting. If specifying, accounts
can be given a bootstrap balance and can also be configured to be bootstrap
baker accounts. Accounts with balances set to "0" will be imported by the
node but they will not be bootstrap accounts. If you don't set a bootstrap
balance, it will default to the
- command: PtMumbai
A public key account can contain a
signer_url to a remote signer
that signs with the corresponding secret key. You don't need to
set this if you're deploying a tezos-k8s signer into the same
namespace of its baker. See
fields in values.yaml to define remote signers. (You shouldn't add things
to the URL path such as the public key hash. It will be added automatically.)
An account being signed for by a Tacoinfra AWS KMS signer requires a
key_id field. This should be a valid id of the AWS KMS key.
The key's corresponding public key must be provided here as well.
When running bakers for a public net, you must provide your own secret keys.
For non public networks you can change the
should_generate_unsafe_deterministic_data setting to true, and deterministic
keys will be generated for your nodes automatically. This is helpful to spin up