Propagate UCAN web3.storage keys in Livepeer services

[leszko]

Update Livepeer Infra configuration to propagate UCAN keys into the following services:

• catalyst: needs Private Key to interact with the w3s up API
• livepeer-api: needs DID (Public Key)

Here are the related configurations which injects Vault secrets as environment variables:

• livepeer
• catalyst

---

Acceptance criteria

• Livepeer Infra configuration is updated with UCAN keys secrets taken from Vault
• Staging catalyst and livepeer-api pods are checked if the keys are visible there in their environment variables (can be checked with kubectl describe pod <pod-name>)
• Environment variables used: LP_API_DID and CATALYST_UCAN_KEY

[red-0ne]

Since catalyst-api is getting its variables as arguments. I propose to not have CATALYST_UCAN_KEY as env variable and let it be passed directly through catalyst-api args (https://github.com/livepeer/catalyst-api/pull/381). If we need the value to be exposed as environment variable, then it should be assigned here I guess livepeer-infra/values/catalyst.values.yaml

[leszko]

Yeah, agree, let's do the same what we do with other flags.

[leszko]

Reopening. Related Discord discussion: https://discord.com/channels/423160867534929930/1006190767510917202/1067432142876987492

[leszko]

The Studio part is done.

The Catalyst API part needs to wait until we introduce the related flag to Catalyst API