-
Task
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
False
-
-
False
-
-
-
Customer Escalated
1. Proposed title of this feature request
====
Alternatives to long-lived SA tokens for configuring metrics in workload availability operators.
2. What is the nature and description of the request?
====
As per documentation, https://docs.redhat.com/en/documentation/workload_availability_for_red_hat_openshift/25.7/html-single/remediation_fencing_and_maintenance/index#configuring-metrics-for-workload-availability-operators_about-node-remediation-fencing-maintenance
To configure metrics for Openshift Workload Availability, we need to create a secret with prometheus SA token and link that secret to Servicemonitor resource.
The documented steps need long-lived SA token for prometheus authentication.
For security reasons, it is mostly recommended not to keep any long-lived unexpired token in cluster.
3. Why does the customer need this?
====
For security reasons, it is mostly recommended not to keep any long-lived unexpired token in cluster.
4. List any affected packages or components.
====
Monitoring, Openshift Workload Availability
- links to