Automate setup with Kubernetes operator
Open
Nobody has claimed this yet.
Epic
- Dominant language
- Go
- Stars
- 12.4k
- Forks
- 510
- PR merge metrics
- No merged PRs in 30d
Description
Deploy toxiproxy to existing environment and modify the resource to route traffic through it.
Requirements:
- Deploy Toxiproxy server
- Create Toxiproxy server config base on CRD
- Modify the deployment pods to have
/etc/hostspointed to Toxiproxy + SNIProxy depends on protocol - Allow to propogate the same command to all Toxiproxy instances (if there is more than one)
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
Begin by locating the repository's Kubernetes operator entry point and CRD definitions; the issue does not name files or tests. Trace how Toxiproxy instances and deployment pods are represented, then define completion against the four listed requirements, including protocol-dependent SNIProxy behavior and propagation to multiple instances.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100