redpanda-data / redpanda-data/openmessaging-benchmark
Prometheus and grafana port should not be accessible from any address, only myip
Open
- Dominant language
- Java
- Stars
- 40
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
This should probably be locked down to same address as used for general access to the security group from the tester's home node.
cidr_blocks = ["${chomp(data.http.myip.body)}/32"]
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 with driver-redpanda/deploy/provision-redpanda-aws.tf lines 176-188 and compare the Prometheus and Grafana ingress rules with the security-group rule for general tester access. Restrict those ports to the tester's myip address, then verify the Terraform configuration and confirm no broader address range remains; an open linked pull request indicates this work is already underway.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, prometheus, terraform
- Domain
- cloud, infrastructure, security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100