hashgraph / hashgraph/full-stack-testing
Don't deploy minio and mirro-node with the network node
Open
Feature Enhancement
- Dominant language
- Java
- Stars
- 9
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Use taints to ensure mirror-node and minio are deployed on desired nodes.
Contributor guide
Research direction
Locate the deployment configuration for the network node, mirror-node, and MinIO, then inspect how node placement is currently defined. Determine which taints and tolerations are needed so mirror-node and MinIO run on the desired nodes rather than the network node. Done means the deployments consistently schedule on the intended nodes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100