hashicorp / hashicorp/vault-secrets-operator
VaultStaticSecrets metrics not available
- Dominant language
- Go
- Stars
- 600
- Forks
- 146
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 6
Description
**Describe the bug**
I'd like to know the status of my VaultStaticSecrets but I'm not clear whether or not this is possible through the `/metrics` endpoint.
Looking at the `controller_resource_status` metric being exposed, the only Controllers reporting are `vaultauth` and `vaultconnection`.
However, it seems the source code shows a few other Controllers and is missing others (e.g. VaultStaticSecret) https://github.com/search?q=repo%3Ahashicorp/vault-secrets-operator%20SetResourceStatus&type=code
**To Reproduce**
Steps to reproduce the behavior:
1. Deploy VSO and enable telemetry
2. Deploy `kube-prometheus-stack`
3. Look at metrics exposed via Prometheus or Grafana and see the absence of controllers such as VaultStaticSecret
**Expected behavior**
I hope to see the current statuses of my VaultStaticSecret resources
**Environment**
* Kubernetes version:
* AKS 1.27.13
* vault-secrets-operator version: 0.8.1
* kube-prometheus-stack version 62.6.0
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the controller_resource_status metric and the SetResourceStatus calls in the vault-secrets-operator source referenced by the issue. Reproduce with telemetry enabled and kube-prometheus-stack, then compare the VaultStaticSecret controller with the controllers already reporting. Done means VaultStaticSecret resource status is exposed through /metrics and is visible in Prometheus or Grafana.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, prometheus
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100