Skip to content

Robot Upgrade: prometheus-node-exporter chart upgrade from 4.6.0 to 4.52.0#3953

Open
weizhoublue wants to merge 1 commit intomainfrom
upgrade/prometheus-node-exporter/4.52.0
Open

Robot Upgrade: prometheus-node-exporter chart upgrade from 4.6.0 to 4.52.0#3953
weizhoublue wants to merge 1 commit intomainfrom
upgrade/prometheus-node-exporter/4.52.0

Conversation

@weizhoublue
Copy link
Member

I am robot, upgrade: project prometheus-node-exporter chart upgrade from 4.6.0 to 4.52.0

@gemini-code-assist
Copy link

Summary of Changes

Hello @weizhoublue, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request delivers a substantial upgrade to the prometheus-node-exporter Helm chart, advancing it to version 4.52.0 and updating the embedded Node Exporter application to 1.10.2. A key feature introduced is the optional integration of kube-rbac-proxy, which enables secure, RBAC-controlled access to the Node Exporter's metrics via HTTPS. The chart has also been modernized by removing deprecated Pod Security Policy configurations and expanding its configurability significantly, offering more granular control over network policies, service definitions, pod monitoring, and resource management.

Highlights

  • Chart Version Upgrade: Upgraded the prometheus-node-exporter Helm chart from version 4.6.0 to 4.52.0, and the underlying Node Exporter appVersion from 1.3.1 to 1.10.2.
  • Kube-RBAC-Proxy Integration: Introduced optional kube-rbac-proxy integration to secure the Node Exporter's metrics endpoint with HTTPS and Kubernetes RBAC authorization, enhancing security posture.
  • Pod Security Policy Removal: Removed all Pod Security Policy (PSP) related resources and configurations, aligning with Kubernetes' deprecation of PSPs.
  • Enhanced Configurability: Added extensive new configuration options for PodMonitor resources, network policies, dual-stack services, detailed affinity settings, and various pod lifecycle parameters.
  • OCI Artifact Support: Updated documentation and internal logic to reflect and support Helm OCI (Open Container Initiative) artifacts for chart distribution and installation.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • charts/prometheus-node-exporter/config
    • Updated the VERSION environment variable to 4.52.0.
  • charts/prometheus-node-exporter/prometheus-node-exporter/Chart.yaml
    • Updated appVersion to 1.10.2 and version to 4.52.0.
    • Added annotations for Artifact Hub, an icon, and url fields for maintainers, including a new maintainer.
    • Updated the dependency version for prometheus-node-exporter to 4.52.0.
  • charts/prometheus-node-exporter/prometheus-node-exporter/README.md
    • Updated documentation for installation and upgrade instructions to reflect OCI artifact usage.
    • Added a new section detailing kube-rbac-proxy configuration.
    • Updated links for ServiceMonitor and PodMonitor documentation.
  • charts/prometheus-node-exporter/prometheus-node-exporter/charts/prometheus-node-exporter/.helmignore
    • Added ci/ to the ignore list.
  • charts/prometheus-node-exporter/prometheus-node-exporter/charts/prometheus-node-exporter/Chart.yaml
    • Updated appVersion to 1.10.2 and version to 4.52.0.
    • Added annotations for Artifact Hub, an icon, and url fields for maintainers, including a new maintainer.
  • charts/prometheus-node-exporter/prometheus-node-exporter/charts/prometheus-node-exporter/README.md
    • Updated documentation for installation and upgrade instructions to reflect OCI artifact usage.
    • Added a new section detailing kube-rbac-proxy configuration.
    • Updated links for ServiceMonitor and PodMonitor documentation.
  • charts/prometheus-node-exporter/prometheus-node-exporter/charts/prometheus-node-exporter/ci/port-values.yaml
    • Removed the file.
  • charts/prometheus-node-exporter/prometheus-node-exporter/charts/prometheus-node-exporter/templates/NOTES.txt
    • Added conditional notes for kubeRBACProxy enablement, detailing HTTPS and RBAC requirements.
  • charts/prometheus-node-exporter/prometheus-node-exporter/charts/prometheus-node-exporter/templates/_helpers.tpl
    • Modified image definition logic to support image.digest and global.imageRegistry, and explicitly disallow image.sha.
    • Introduced new helper templates for imagePullSecrets, podmonitor-namespace, podmonitor.scrapeLimits, sidecarVolumeMounts, defaultAffinity, and mergedAffinities.
  • charts/prometheus-node-exporter/prometheus-node-exporter/charts/prometheus-node-exporter/templates/clusterrole.yaml
    • Added a new ClusterRole for kubeRBACProxy to grant necessary tokenreviews and subjectaccessreviews permissions.
  • charts/prometheus-node-exporter/prometheus-node-exporter/charts/prometheus-node-exporter/templates/clusterrolebinding.yaml
    • Added a new ClusterRoleBinding for kubeRBACProxy to link the service account to the new ClusterRole.
  • charts/prometheus-node-exporter/prometheus-node-exporter/charts/prometheus-node-exporter/templates/daemonset.yaml
    • Added revisionHistoryLimit, podLabels, terminationGracePeriodSeconds, hostUsers, hostIPC, dnsPolicy, and restartPolicy fields.
    • Updated automountServiceAccountToken logic to account for kubeRBACProxy.
    • Modified HOST_IP and web.listen-address to support kubeRBACProxy and dynamic service ports.
    • Added --path.udev.data argument for newer Node Exporter versions.
    • Adjusted liveness and readiness probes for kubeRBACProxy integration.
    • Added terminationMessagePath and terminationMessagePolicy parameters.
    • Included mountPropagation for proc and sys volume mounts.
    • Refactored sidecar container definition and added the kube-rbac-proxy container.
    • Updated imagePullSecrets and affinity to use new helper templates.
    • Added kube-rbac-proxy-config and tlsSecret volumes, and extraVolumes.
  • charts/prometheus-node-exporter/prometheus-node-exporter/charts/prometheus-node-exporter/templates/extra-manifests.yaml
    • Added a template to include extra Kubernetes manifests.
  • charts/prometheus-node-exporter/prometheus-node-exporter/charts/prometheus-node-exporter/templates/networkpolicy.yaml
    • Added a template for NetworkPolicy resource creation.
  • charts/prometheus-node-exporter/prometheus-node-exporter/charts/prometheus-node-exporter/templates/podmonitor.yaml
    • Added a template for PodMonitor resource creation.
  • charts/prometheus-node-exporter/prometheus-node-exporter/charts/prometheus-node-exporter/templates/psp-clusterrole.yaml
    • Removed the Pod Security Policy ClusterRole template.
  • charts/prometheus-node-exporter/prometheus-node-exporter/charts/prometheus-node-exporter/templates/psp-clusterrolebinding.yaml
    • Removed the Pod Security Policy ClusterRoleBinding template.
  • charts/prometheus-node-exporter/prometheus-node-exporter/charts/prometheus-node-exporter/templates/psp.yaml
    • Removed the Pod Security Policy template.
  • charts/prometheus-node-exporter/prometheus-node-exporter/charts/prometheus-node-exporter/templates/rbac-configmap.yaml
    • Added a ConfigMap for kube-rbac-proxy authorization configuration.
  • charts/prometheus-node-exporter/prometheus-node-exporter/charts/prometheus-node-exporter/templates/service.yaml
    • Wrapped the service definition with a conditional service.enabled.
    • Added service.labels, ipDualStack, externalTrafficPolicy, internalTrafficPolicy, and clusterIP fields.
    • Modified port configuration to use servicePort if specified.
  • charts/prometheus-node-exporter/prometheus-node-exporter/charts/prometheus-node-exporter/templates/serviceaccount.yaml
    • Added automountServiceAccountToken and updated imagePullSecrets to use the new helper.
  • charts/prometheus-node-exporter/prometheus-node-exporter/charts/prometheus-node-exporter/templates/servicemonitor.yaml
    • Added podTargetLabels, targetLabels, and attachMetadata fields to the ServiceMonitor specification.
  • charts/prometheus-node-exporter/prometheus-node-exporter/charts/prometheus-node-exporter/templates/verticalpodautoscaler.yaml
    • Added recommenders and controlledValues fields.
    • Updated containerName to node-exporter and modified updatePolicy handling.
  • charts/prometheus-node-exporter/prometheus-node-exporter/charts/prometheus-node-exporter/values.yaml
    • Updated image configuration to use registry and digest.
    • Added nameOverride, fullnameOverride, revisionHistoryLimit, and global settings.
    • Introduced comprehensive kubeRBACProxy and tlsSecret configuration sections.
    • Expanded service configuration with enabled, clusterIP, servicePort, labels, ipDualStack, externalTrafficPolicy, and internalTrafficPolicy.
    • Added networkPolicy and prometheus.podMonitor configuration sections.
    • Added restartPolicy, hostUsers, hostIPC, hostProcFsMount, hostSysFsMount, terminationGracePeriodSeconds, terminationMessageParams, extraManifests, extraVolumes, extraVolumeMounts, and version fields.
    • Removed pspEnabled and pspAnnotations from rbac.
    • Updated containerSecurityContext to include readOnlyRootFilesystem: true.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request upgrades the prometheus-node-exporter Helm chart from version 4.6.0 to 4.52.0. This is a significant update, incorporating numerous features and improvements from the upstream chart, such as kube-rbac-proxy support, PodMonitor resources, and the removal of deprecated PodSecurityPolicy objects. The changes are well-aligned with the upstream chart. My review includes a minor suggestion to improve consistency in the configuration of container image digests.

Comment on lines +219 to +223
{{- if .Values.kubeRBACProxy.image.sha }}
image: "{{ .Values.global.imageRegistry | default .Values.kubeRBACProxy.image.registry}}/{{ .Values.kubeRBACProxy.image.repository }}:{{ .Values.kubeRBACProxy.image.tag }}@sha256:{{ .Values.kubeRBACProxy.image.sha }}"
{{- else }}
image: "{{ .Values.global.imageRegistry | default .Values.kubeRBACProxy.image.registry}}/{{ .Values.kubeRBACProxy.image.repository }}:{{ .Values.kubeRBACProxy.image.tag }}"
{{- end }}

Choose a reason for hiding this comment

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

medium

For consistency with how the main node-exporter image is handled in _helpers.tpl, the kube-rbac-proxy image should use digest instead of sha. The digest field is expected to contain the full digest string including the algorithm (e.g., sha256:...). This also makes the template more flexible if a different hash algorithm is used in the future.

          {{- if .Values.kubeRBACProxy.image.digest }}
          image: "{{ .Values.global.imageRegistry | default .Values.kubeRBACProxy.image.registry}}/{{ .Values.kubeRBACProxy.image.repository }}:{{ .Values.kubeRBACProxy.image.tag }}@{{ .Values.kubeRBACProxy.image.digest }}"
          {{- else }}
          image: "{{ .Values.global.imageRegistry | default .Values.kubeRBACProxy.image.registry}}/{{ .Values.kubeRBACProxy.image.repository }}:{{ .Values.kubeRBACProxy.image.tag }}"
          {{- end }}

registry: quay.io
repository: brancz/kube-rbac-proxy
tag: v0.21.0
sha: ""

Choose a reason for hiding this comment

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

medium

To align with the main image configuration and the suggested change in daemonset.yaml, this should be digest instead of sha.

    digest: ""

@github-actions github-actions bot force-pushed the upgrade/prometheus-node-exporter/4.52.0 branch from d02c842 to c912ba1 Compare February 27, 2026 20:15
…4.52.0

Signed-off-by: robot <robot@example.com>
@github-actions github-actions bot force-pushed the upgrade/prometheus-node-exporter/4.52.0 branch from c912ba1 to bee9392 Compare February 28, 2026 20:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants