Kuadrant / Kuadrant/dns-operator
Investigate whether DNSRecord deletion are persisted when running at scale
- Dominant language
- Go
- Stars
- 12
- Forks
- 23
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 14
Description
**What**
Test against AWS, Azure and GCP (most likely to occur in AWS and Azure).
```
make local-setup DEPLOY=true DEPLOYMENT_SCOPE=namespace DEPLOYMENT_COUNT=20
make test-e2e-multi TEST_DNS_MANAGED_ZONE_NAME=dev-mz-aws TEST_DNS_NAMESPACES=dns-operator DEPLOYMENT_COUNT=20
```
See if there is significant delays in verifying removal of records; if so, create a follow on ticket to improve the efficiency of the verification code.
Contributor guide
Research direction
Start with the provided make local-setup and make test-e2e-multi commands, using the listed deployment count and DNS settings. Compare DNSRecord deletion verification across AWS, Azure and GCP; done means determining whether significant delays occur and, if they do, opening a follow-on ticket for verification efficiency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure, gcp, go
- Domain
- cloud, infrastructure, performance, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100