Skip to content

Conversation

simonpasquier
Copy link
Contributor

@simonpasquier simonpasquier commented Aug 25, 2025

This change updates jsonnet dependencies to their latest versions. In particular, it freezes the node_exporter and Prometheus dashboards to the latest versions supporting Grafana 11. From now on, these dashboards will no longer receive updates from the upstream mixins (until we migrate to the upstream Perses dashboards).

The PR can wait after the 4.20 branch cut

  • I added CHANGELOG entry for this change.
  • No user facing changes, so no entry in CHANGELOG was needed.

@openshift-ci openshift-ci bot requested review from machine424 and rexagod August 25, 2025 10:40
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 25, 2025
@simonpasquier simonpasquier changed the title chore: bump jsonnet dependencies NO-JIRA: chore: bump jsonnet dependencies Aug 25, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 25, 2025
@openshift-ci-robot
Copy link
Contributor

@simonpasquier: This pull request explicitly references no jira issue.

In response to this:

This change updates jsonnet dependencies to their latest versions. In particular, it freezes the node_exporter and Prometheus dashboards to the latest versions supporting Grafana 11. From now on, these dashboards will no longer receive updates from the upstream mixins (until we migrate to the upstream Perses dashboards).

  • I added CHANGELOG entry for this change.
  • No user facing changes, so no entry in CHANGELOG was needed.

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 openshift-eng/jira-lifecycle-plugin repository.

@simonpasquier
Copy link
Contributor Author

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 25, 2025
@simonpasquier
Copy link
Contributor Author

/skip

@simonpasquier
Copy link
Contributor Author

/skip

Copy link
Contributor

@machine424 machine424 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
thanks!

@@ -32,9 +32,10 @@ spec:
automountServiceAccountToken: true
containers:
- args:
- --web.listen-address=127.0.0.1:9100
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, using the same port on different interfaces can confusing, plus a pod has plenty of them

@@ -278,6 +278,15 @@ spec:
for: 15m
labels:
severity: warning
- alert: NodeSystemdServiceCrashlooping
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we'd need a ticket to understand and add a runbook for this one.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've opted for removing the alerting rule: the systemd collector isn't enabled by default + when it is, users can define their own AlertingRule custom resource (they probably do already).

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 29, 2025
Copy link
Contributor

openshift-ci bot commented Aug 29, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: machine424, 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:
  • OWNERS [machine424,simonpasquier]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@simonpasquier
Copy link
Contributor Author

/hold cancel

removing the hold since we're in acknowledge-critical-fixes-only phase anyway.

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 29, 2025
This change updates jsonnet dependencies to their latest versions. In
particular, it freezes the node_exporter and Prometheus dashboards to
the latest versions supporting Grafana 11. From now on, these dashboards
will no longer receive updates from the upstream mixins (until we
migrate to the upstream Perses dashboards).

Signed-off-by: Simon Pasquier <[email protected]>
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Sep 3, 2025
Copy link
Contributor

openshift-ci bot commented Sep 3, 2025

New changes are detected. LGTM label has been removed.

@simonpasquier
Copy link
Contributor Author

/retest-required

1 similar comment
@simonpasquier
Copy link
Contributor Author

/retest-required

Copy link
Contributor

openshift-ci bot commented Sep 3, 2025

@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-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants