Kuadrant / Kuadrant/dns-operator
Allow user to define whether or not a geo can be fully removed
Open
- Dominant language
- Go
- Stars
- 12
- Forks
- 23
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 14
Description
With the out-of-the-box soft delete we could potentially remove the entire geo.
We need to explicitly let the user decide how they want to handle the scenario when their geo is not healthy.
Contributor guide
Research direction
Start by tracing the out-of-the-box soft-delete handling and the path used when a geo is unhealthy. Define the user-configurable behavior for whether the entire geo may be removed, then verify that both choices produce the intended outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100