Enable metrics for the agentic controller operand
- Dominant language
- Jinja
- Stars
- 37
- Forks
- 49
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 22
Description
## Summary
Enable metrics for the agentic controller operand in konveyor/operator. The initial operand PR (konveyor/operator#591) ships with metrics **disabled** (`--metrics-bind-address=0`, no Service/ServiceMonitor) to keep scope small.
## Scope
Mirror the existing hub metrics pattern in the operator (`roles/tackle/templates/servicemonitor-hub.yml.j2`, `hub_metrics_enabled`):
- Enable the controller metrics endpoint (`--metrics-bind-address`), with secure serving + metrics-auth as appropriate.
- cert-manager wiring for the metrics certificate (the controller supports `--metrics-cert-path`).
- A ServiceMonitor for the agentic controller, gated behind an `agentic_metrics_enabled`-style flag consistent with `hub_metrics_enabled`.
Related: konveyor/operator#591
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading roles/tackle/templates/servicemonitor-hub.yml.j2 and the hub_metrics_enabled pattern, then compare the agentic controller setup from konveyor/operator#591. Done means the agentic controller exposes securely served metrics, has cert-manager wiring, and provides a ServiceMonitor controlled by an agentic_metrics_enabled-style flag.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100