Enable telemetry reporting for cluster-monitoring-operator #46589
Conversation
|
/hold I need to update the 4.x configs too. |
openshift-ci
bot
added
do-not-merge/hold
|
/pj-rehearse |
|
The rehearsed e2e-aws-ovn job shows that telemtry is enabled: Compare to a recent run of the job (openshift/cluster-monitoring-operator#2189) reporting that telemetry is disabled: |
|
/pj-rehearsals-ack |
|
/cc @jan--f |
simonpasquier
force-pushed
the
enable-telemetry-cmo
branch
from
1937574
to
ec5ade1
Compare
|
/hold cancel All jobs from 4.12 to 4.16 updated. |
openshift-ci
bot
removed
the
do-not-merge/hold
The cluster-monitoring-operator jobs need to have telemetry reporting enabled because the operator is responsible for deploying the telemeter-client component. Signed-off-by: Simon Pasquier <spasquie@redhat.com>
simonpasquier
force-pushed
the
enable-telemetry-cmo
branch
from
ec5ade1
to
1e48681
Compare
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearsals-ack |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jan--f, simonpasquier The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/pj-rehearse ack |
openshift-ci-robot
added
the
rehearsals-ack
|
@simonpasquier: all tests passed! Full PR test history. Your PR dashboard. 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/test-infra repository. I understand the commands that are listed here. |
The cluster-monitoring-operator jobs need to have telemetry reporting enabled because the operator is responsible for deploying the telemeter-client component.