Add tests for DNS Failover
- Dominant language
- Python
- Stars
- 7
- Forks
- 29
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
**Summary**
Add new multi-cluster tests for DNS Operator DNS Failover. Tests should be marked as disruptive as they would need to change dns operator `GROUP` variable and restart the controller
**Documentation**
Related docs for DNS Failover are in https://github.com/Kuadrant/dns-operator/tree/main/docs
**Test cases**
- [ ] Configure 1 active and 1 passive group on 2 clusters, switch active groups
- [ ] Configure 2 active groups with a shared record, see these records enforced and merged
Consider these additional tests or asserts:
- [ ] Check records on provider are removed when deleted inside inactive group (that was active)
- [ ] Check records on provider are kept when changing to inactive group (without overwriting active group)
Contributor guide
Research direction
Start by reading the DNS Failover documentation in the dns-operator docs linked in the issue, then locate the tests and setup used for multi-cluster scenarios. Verify the two listed failover cases and the additional provider-record assertions, marking the tests disruptive because they change the DNS operator GROUP variable and restart the controller.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems, networking, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100