Kuadrant / Kuadrant/dns-operator
Tracing Support
- Dominant language
- Go
- Stars
- 12
- Forks
- 23
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 14
Description
# Description
Since https://github.com/Kuadrant/kuadrant-operator/issues/1690 has been done to Limitador Operator and the control plane portion of Authorino, do we also want to support tracing in DNS Operator?
If we do, the ask is:
- Support tracing in dns operator
- Support trace propagation linking via CR annotation
Sample PRs:
- https://github.com/Kuadrant/authorino/pull/574
- https://github.com/Kuadrant/limitador-operator/pull/222
- https://github.com/Kuadrant/kuadrant-operator/pull/1717
Contributor guide
Research direction
Start by reviewing the related issue #1690 and the sample PRs in Authorino, Limitador Operator, and Kuadrant Operator to understand their tracing approach. Then inspect the DNS Operator's existing tracing and CR annotation entry points, if present. Done means tracing is supported and trace propagation links are handled through the CR annotation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure, observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100