Kuadrant / Kuadrant/dns-operator
Investigate: multi cluster secrets to self
- Dominant language
- Go
- Stars
- 12
- Forks
- 23
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 14
Description
What happens in the multi cluster setup if a primary cluster has a cluster secret that points to its self.
This would be user error in the configuration of the multi cluster setup, but how does the operator handle this.
**Acceptable outcome**
If there is an issue with creating a cluster secret on a primary for that primary, documenting the edge case maybe a reasonable fix.
Contributor guide
Research direction
No file or test is named. Start by tracing the multi-cluster handling for cluster secrets that reference the primary cluster itself, then determine how the operator behaves for this configuration. Done means the behavior is established and either the handling is validated or the edge case is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100