fix: openshift-gitops-operator-metrics-monitor ServiceMonitor is attempting to use a bearerTokenFile configuration in its endpoints definition - #1005
Conversation
…mpting to use a bearerTokenFile configuration in its endpoints definition Signed-off-by: akhil nittala <[email protected]>
|
Skipping CI for Draft Pull Request. |
…mpting to use a bearerTokenFile configuration in its endpoints definition Signed-off-by: akhil nittala <[email protected]>
…mpting to use a bearerTokenFile configuration in its endpoints definition Signed-off-by: akhil nittala <[email protected]>
…mpting to use a bearerTokenFile configuration in its endpoints definition Signed-off-by: akhil nittala <[email protected]>
…mpting to use a bearerTokenFile configuration in its endpoints definition Signed-off-by: akhil nittala <[email protected]>
|
/retest |
|
/retest-required |
…mpting to use a bearerTokenFile configuration in its endpoints definition Signed-off-by: akhil nittala <[email protected]>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: svghadi The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/cherry-pick v1.19 |
|
@svghadi: once the present PR merges, I will cherry-pick it on top of DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
e941094
into
redhat-developer:master
|
@svghadi: new pull request created: #1014 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@svghadi: #1005 failed to apply on top of branch "v1.18": DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@svghadi: #1005 failed to apply on top of branch "v1.17": DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
…mpting to use a bearerTokenFile configuration in its endpoints definition (redhat-developer#1005) * fix: openshift-gitops-operator-metrics-monitor ServiceMonitor is attempting to use a bearerTokenFile configuration in its endpoints definition Signed-off-by: akhil nittala <[email protected]> * fix: openshift-gitops-operator-metrics-monitor ServiceMonitor is attempting to use a bearerTokenFile configuration in its endpoints definition Signed-off-by: akhil nittala <[email protected]> * fix: openshift-gitops-operator-metrics-monitor ServiceMonitor is attempting to use a bearerTokenFile configuration in its endpoints definition Signed-off-by: akhil nittala <[email protected]> * fix: openshift-gitops-operator-metrics-monitor ServiceMonitor is attempting to use a bearerTokenFile configuration in its endpoints definition Signed-off-by: akhil nittala <[email protected]> * fix: openshift-gitops-operator-metrics-monitor ServiceMonitor is attempting to use a bearerTokenFile configuration in its endpoints definition Signed-off-by: akhil nittala <[email protected]> * fix: openshift-gitops-operator-metrics-monitor ServiceMonitor is attempting to use a bearerTokenFile configuration in its endpoints definition Signed-off-by: akhil nittala <[email protected]> --------- Signed-off-by: akhil nittala <[email protected]> Signed-off-by: Atif Ali <[email protected]>
What type of PR is this?
/kind bug
What does this PR do / why we need it:
The latest Prometheus upgrade enforces stricter security practices by requiring the use of Secrets and ConfigMaps for bearer tokens and TLS CA configurations. However, our current implementation references bearerTokenFile and tlsConfig.caFile using absolute filesystem paths. This approach is no longer permitted, as Prometheus now prohibits direct filesystem access for these files. As a result, the Prometheus Operator logs show errors when it attempts to access these paths.
Have you updated the necessary documentation?
Which issue(s) this PR fixes:
https://issues.redhat.com/browse/GITOPS-7992
Fixes #?
https://issues.redhat.com/browse/GITOPS-7992
Test acceptance criteria:
How to test changes / Special notes to the reviewer:
install gitops operator on oc cluster
make this change in cluster-monitoring-configmap like below