fix: openshift-gitops-operator-metrics-monitor ServiceMonitor is attempting to use a bearerTokenFile configuration in its endpoints definition - #1027
Merged
openshift-merge-bot[bot] merged 2 commits intoDec 9, 2025
Conversation
…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]>
akhilnittala
force-pushed
the
usr/akhil/GITOPS-7992_1.17
branch
from
December 8, 2025 07:41
6b919b5 to
6f471b6
Compare
This was referenced Dec 8, 2025
anandf
approved these changes
Dec 9, 2025
Member
|
/lgtm |
Member
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: anandf 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 |
openshift-merge-bot
Bot
merged commit Dec 9, 2025
846a2ea
into
redhat-developer:v1.17
10 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
kind: ConfigMap
apiVersion: v1
metadata:
name: cluster-monitoring-config
namespace: openshift-monitoring
uid: 8d390161-acc1-4409-809d-638359caeb40
resourceVersion: '1966303'
creationTimestamp: '2025-11-08T20:14:19Z'
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"v1","data":{"config.yaml":"prometheusK8s:\n retention: 3d\n"},"kind":"ConfigMap","metadata":{"annotations":{},"name":"cluster-monitoring-config","namespace":"openshift-monitoring"}}
managedFields:
- manager: kubectl-client-side-apply
operation: Update
apiVersion: v1
time: '2025-11-08T20:14:19Z'
fieldsType: FieldsV1
fieldsV1:
'f:data': {}
'f:metadata':
'f:annotations':
.: {}
'f:kubectl.kubernetes.io/last-applied-configuration': {}
- manager: Mozilla
operation: Update
apiVersion: v1
time: '2025-11-13T08:48:04Z'
fieldsType: FieldsV1
fieldsV1:
'f:data':
'f:config.yaml': {}
data:
config.yaml: |
enableUserWorkload: true
prometheusK8s:
retention: 3d
check prometheus operator pod logs using command "oc logs -f prometheus-operator-b6ccc8c9d-s86q4 -n openshift-user-workload-monitoring"