paritytech / paritytech/testnet-manager
Add fallbacks when NAMESPACE, RELAY_CHAIN_RPC_URL or RPC_NODE_URL_PATTERN are not set
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Some base env vars are currently required to start the testnet-manager properly but I think we should be able to remove this requirements which would make the app work out of the box when deployed to a namespace which contains running nodes deployed with our helm-chart.
NAMESPACE: call this variableRELAY_CHAIN_NAMEinstead which would allow having a chain name different from the namespace name then use the content of/var/run/secrets/kubernetes.io/serviceaccount/namespaceas defaultRELAY_CHAIN_RPC_URL: find pods running with the labelchain=RELAY_CHAIN_NAMEthen try to query itRPC_NODE_URL_PATTERN: use "NODE_NAME:9944", it is possible now as we no longer have to support both 9933/9944
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the startup handling for NAMESPACE, RELAY_CHAIN_RPC_URL, and RPC_NODE_URL_PATTERN, then inspect how the helm-chart exposes running nodes and how pods are queried. Done means the testnet-manager starts without those variables, uses the service-account namespace and NODE_NAME:9944 defaults, and discovers pods labeled chain=RELAY_CHAIN_NAME.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, python
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100