It is common practice for secrets to be created separately by a secret manager, and the Helm chart should accommodate this usage. Previously, it was only possible to configure the key for a single Substrate node, which limited the stateful set to a replica count of one.
This PR introduces the ability to use node.existingSecrets.extraDerivation, enabling the same seed key to be utilized across multiple nodes. Furthermore, it adds support for node.existingSecrets.nodeKey.appendPodIndex for node key secrets, allowing multiple node keys to be stored within the same Kubernetes secret.
Changes
Added support for extraDerivation.
Included an example for node.existingSecrets usage.
It is common practice for secrets to be created separately by a secret manager, and the Helm chart should accommodate this usage. Previously, it was only possible to configure the key for a single Substrate node, which limited the stateful set to a replica count of one.
This PR introduces the ability to use
node.existingSecrets.extraDerivation, enabling the same seed key to be utilized across multiple nodes. Furthermore, it adds support fornode.existingSecrets.nodeKey.appendPodIndexfor node key secrets, allowing multiple node keys to be stored within the same Kubernetes secret.Changes
extraDerivation.node.existingSecretsusage.