-
Notifications
You must be signed in to change notification settings - Fork 30
Closed as not planned
Labels
kind/enhancementCategorizes issue or PR as related to an improvement.Categorizes issue or PR as related to an improvement.lifecycle/staleDenotes an issue or PR that has become stale and will be auto-closed.Denotes an issue or PR that has become stale and will be auto-closed.
Description
Preflight Checklist
- I have searched the issue tracker for an issue that matches the one I want to file, without success.
- I agree to follow the Code of Conduct.
Problem Description
Currently, the Vault Operator only logs reconciliation errors (like “failed to distribute CA secret for vault”) without raising Kubernetes Events. This makes debugging difficult, since users must inspect operator logs instead of using kubectl describe or kubectl get events.
Proposed Solution
Raising event for failure scenarios (e.g. CA secret distribution, sync failures, etc.) using the standard r.recorder.Event() mechanism, for example:
r.recorder.Eventf(vault, "Error", "CASecretDistributionFailed", "Failed to distribute CA secret: %v", err)This would improve visibility, monitoring, and user experience by surfacing issues directly on Vault Objects.
I’d be happy to implement this feature if it’s accepted.
Alternatives Considered
No response
Additional Information
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind/enhancementCategorizes issue or PR as related to an improvement.Categorizes issue or PR as related to an improvement.lifecycle/staleDenotes an issue or PR that has become stale and will be auto-closed.Denotes an issue or PR that has become stale and will be auto-closed.