[{"_1":2,"_139":-5,"_140":-5},"loaderData",{"_3":4,"_17":18,"_25":26,"_133":134},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","routes/_layout",{"_19":-5,"_20":21,"_22":21,"_23":11,"_24":21},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)",{"_27":28,"_29":30,"_59":60,"_61":-7,"_62":-7,"_63":-7,"_64":-7,"_65":-5,"_66":-5,"_67":11,"_68":11,"_52":69,"_123":21,"_91":92,"_124":90,"_125":51,"_35":36,"_126":11,"_127":21,"_128":129,"_130":-5,"_131":11,"_132":11},"scanningType","none","tagData",{"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":42,"_43":44,"_45":34,"_46":47,"_48":49,"_50":51,"_52":53,"_54":-5,"_55":44,"_56":57,"_58":21},"content_type","image","creator",29930447,"digest","sha256:966a3e2ed69309686df684c6999366f8b7e7188224665f46c49befae873f8d96","full_size",7947,"id",912724124,"images",[],"last_updated","2025-06-06T15:51:09.172025Z","last_updater","last_updater_username","bitnamirobot","media_type","application/vnd.oci.image.index.v1+json","name","sha256-b188a739cd7fadb587ff2e481ea1a66e8fb9563cbf7466e4d63b07e322628535","repository",19064368,"tag_last_pulled","tag_last_pushed","tag_status","inactive","v2","tagImages",[],"layerOrdinals","packageName","cveId","sbom","scoutSummary","staticSummary","isScoutPaymentRequired","canSeeVulnerabilities",{"_70":71,"_76":77,"_79":80,"_81":82,"_83":11,"_43":84,"_85":86,"_87":88,"_50":90,"_91":92,"_93":94,"_95":-5,"_96":97,"_98":99,"_100":101,"_102":-5,"_103":97,"_104":105,"_106":11,"_107":92,"_108":109,"_114":11,"_115":116,"_120":92,"_121":122},"categories",[72],{"_50":73,"_74":75},"Monitoring & observability","slug","monitoring-and-observability","content_types",[32,78],"helm","date_registered","2023-01-24T10:51:06.116697Z","description","Bitnami Helm chart for Node Exporter","is_private","2025-08-14T19:21:35.91019Z","last_modified","2026-03-16T14:24:54.567242Z","media_types",[89,49],"application/vnd.cncf.helm.config.v1+json","node-exporter","namespace","bitnamicharts","pull_count",847467,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","\n\n# Bitnami Secure Images Helm chart for Node Exporter\n\nPrometheus exporter for hardware and OS metrics exposed by UNIX kernels, with pluggable metric collectors.\n\n[Overview of Node Exporter](https://prometheus.io/)\n\nTrademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.\n\n## TL;DR\n\n```console\nhelm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/node-exporter\n```\n\n> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository.\n\n## Introduction\n\nThis chart bootstraps [Node Exporter](https://github.com/bitnami/containers/tree/main/bitnami/node-exporter) on [Kubernetes](https://kubernetes.io) using the [Helm](https://helm.sh) package manager.\n\n## Before you begin\n\n- Kubernetes 1.23+\n- Helm 3.8.0+\n\n## Installing the Chart\n\nTo install the chart with the release name `my-release`:\n\n```console\nhelm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/node-exporter\n```\n\n> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.\n\nThe command deploys Node Exporter on the Kubernetes cluster in the default configuration. The [configuration](#configuration-and-installation-details) section lists the parameters that can be configured during installation.\n\n## Configuration and installation details\n\nThis section describes credentials, configuration, and other installation options.\n\n### Resource requests and limits\n\nBitnami charts allow setting resource requests and limits for all containers inside the chart deployment. These are inside the `resources` value (check parameter table). Setting requests is essential for production workloads and these should be adapted to your specific use case.\n\nTo make this process easier, the chart contains the `resourcesPreset` values, which automatically sets the `resources` section according to different presets. Check these presets in [the bitnami/common chart](https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15). However, in production workloads using `resourcesPreset` is discouraged as it may not fully adapt to your specific needs. Find more information on container resource management in the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/).\n\n### [Rolling vs Immutable tags](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/apps-tutorials-understand-rolling-tags-containers-index.html)\n\nIt is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.\n\nBitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.\n\n### Backup and restore\n\nTo back up and restore Helm chart deployments on Kubernetes, you need to back up the persistent volumes from the source deployment and attach them to a new deployment using [Velero](https://velero.io/), a Kubernetes backup/restore tool. Find the instructions for using Velero in [this guide](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/apps-tutorials-backup-restore-deployments-velero-index.html).\n\n### FIPS parameters\n\nThe FIPS parameters only have effect if you are using images from the [Bitnami Secure Images catalog](https://go-vmware.broadcom.com/contact-us).\n\nFor more information on this new support, please refer to the [FIPS Compliance section](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/security-frameworks-FIPS-compliance.html).\n\n### Set Pod affinity\n\nThis chart allows you to set custom Pod affinity using the `affinity` parameter(s). Find more information about Pod affinity in the [Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).\n\nAs an alternative, you can use the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.\n\n### Resource Type\n\nThis chart, by default, installs Node Exporter as a `DaemonSet`. There are some cases where you may need to run Node Exporter as a `Deployment` (e.g., when using its text file collector exclusively). In these instances, you can install the helm chart by setting the `resourceType` parameter to `Deployment`.\n\nInstalling the Node Exporter chart in `Deployment` mode will overwrite `hostNetwork` and `hostPid` to `false` and will not mount `/proc` and `/sys` from the host to the container. You can control this behavior by setting the `isolatedDeployment` parameter.\n\n## Parameters\n\nThe following subsections list global, common, and component-specific parameters.\n\n### Global parameters\n\n| Name | Description | Value |\n| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ |\n| `global.imageRegistry` | Global Docker image registry | `\"\"` |\n| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` |\n| `global.defaultStorageClass` | Global default StorageClass for Persistent Volume(s) | `\"\"` |\n| `global.storageClass` | DEPRECATED: use global.defaultStorageClass instead | `\"\"` |\n| `global.defaultFips` | Default value for the FIPS configuration (allowed values: '', restricted, relaxed, off). Can be overridden by the 'fips' object | `restricted` |\n| `global.security.allowInsecureImages` | Allows skipping image verification | `false` |\n| `global.compatibility.openshift.adaptSecurityContext` | Adapt the securityContext sections of the deployment to make them compatible with Openshift restricted-v2 SCC: remove runAsUser, runAsGroup and fsGroup and let the platform use their allowed default IDs. Possible values: auto (apply if the detected running cluster is Openshift), force (perform the adaptation always), disabled (do not perform adaptation) | `auto` |\n\n### Common parameters\n\n| Name | Description | Value |\n| ------------------------ | -------------------------------------------------------------------------------------------- | --------------- |\n| `kubeVersion` | Force target Kubernetes version (using Helm capabilities if not set) | `\"\"` |\n| `nameOverride` | String to partially override common.names.fullname template (will maintain the release name) | `\"\"` |\n| `fullnameOverride` | String to fully override `common.names.fullname` template with a string | `\"\"` |\n| `namespaceOverride` | String to fully override common.names.namespace | `\"\"` |\n| `commonAnnotations` | Annotations to add to all deployed objects | `{}` |\n| `commonLabels` | Labels to add to all deployed objects | `{}` |\n| `extraDeploy` | Array of extra objects to deploy with the release | `[]` |\n| `clusterDomain` | Kubernetes cluster domain name | `cluster.local` |\n| `diagnosticMode.enabled` | Enable diagnostic mode (all probes will be disabled and the command will be overridden) | `false` |\n| `diagnosticMode.command` | Command to override all containers in the the deployment(s)/statefulset(s) | `[\"sleep\"]` |\n| `diagnosticMode.args` | Args to override all containers in the the deployment(s)/statefulset(s) | `[\"infinity\"]` |\n\n### Node Exporter parameters\n\n| Name | Description | Value |\n| --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------- |\n| `resourceType` | Specify how to deploy Node Exporter (allowed values: `daemonset` and `deployment`) | `daemonset` |\n| `replicaCount` | Number of replicas to deploy (when `resourceType` is `deployment`) | `1` |\n| `isolatedDeployment` | Specify whether to deploy the Node Exporter in an isolated deployment without access to host network, host PID and /proc and /sys of the host. (when `resourceType` is `deployment`) | `true` |\n| `automountServiceAccountToken` | Mount Service Account token in pod | `false` |\n| `hostAliases` | Deployment pod host aliases | `[]` |\n| `runtimeClassName` | Name of the runtime class to be used by pod(s) | `\"\"` |\n| `rbac.create` | Whether to create and use RBAC resources or not | `true` |\n| `rbac.pspEnabled` | Whether to create a PodSecurityPolicy and bound it with RBAC. WARNING: PodSecurityPolicy is deprecated in Kubernetes v1.21 or later, unavailable in v1.25 or later | `true` |\n| `rbac.rules` | Custom RBAC rules to set | `[]` |\n| `serviceAccount.create` | Specifies whether a ServiceAccount should be created | `true` |\n| `serviceAccount.name` | Name of the service account to use. If not set and create is true, a name is generated using the fullname template. | `\"\"` |\n| `serviceAccount.automountServiceAccountToken` | Automount service account token for the server service account | `false` |\n| `serviceAccount.annotations` | Annotations for service account. Evaluated as a template. Only used if `create` is `true`. | `{}` |\n| `image.registry` | Node Exporter image registry | `REGISTRY_NAME` |\n| `image.repository` | Node Exporter image repository | `REPOSITORY_NAME/node-exporter` |\n| `image.digest` | Node Exporter image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `\"\"` |\n| `image.pullPolicy` | Node Exporter image pull policy | `IfNotPresent` |\n| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |\n| `containerPorts.metrics` | Node Exporter container port | `9100` |\n| `sidecars` | Add additional sidecar containers to the Node exporter pod(s) | `[]` |\n| `initContainers` | Add additional init containers to the Node exporter pod(s) | `[]` |\n| `pdb.create` | Enable/disable a Pod Disruption Budget creation | `true` |\n| `pdb.minAvailable` | Minimum number/percentage of pods that should remain scheduled | `\"\"` |\n| `pdb.maxUnavailable` | Maximum number/percentage of pods that may be made unavailable. Defaults to `1` if both `pdb.minAvailable` and `pdb.maxUnavailable` are empty. | `\"\"` |\n| `extraArgs` | Additional command line arguments to pass to node-exporter | `{}` |\n| `command` | Override default container command (useful when using custom images) | `[]` |\n| `args` | Override default container args (useful when using custom images) | `[]` |\n| `lifecycleHooks` | for the Node exporter container(s) to automate configuration before or after startup | `{}` |\n| `extraEnvVars` | Array with extra environment variables to add to Node exporter container | `[]` |\n| `extraEnvVarsCM` | Name of existing ConfigMap containing extra env vars for Node exporter container | `\"\"` |\n| `extraEnvVarsSecret` | Name of existing Secret containing extra env vars for Node exporter container | `\"\"` |\n| `extraVolumes` | Additional volumes to the node-exporter pods | `[]` |\n| `extraVolumeMounts` | Additional volumeMounts to the node-exporter container | `[]` |\n| `podSecurityContext.enabled` | Enabled Node exporter pods' Security Context | `true` |\n| `podSecurityContext.fsGroupChangePolicy` | Set filesystem group change policy | `Always` |\n| `podSecurityContext.sysctls` | Set kernel settings using the sysctl interface | `[]` |\n| `podSecurityContext.supplementalGroups` | Set filesystem extra groups | `[]` |\n| `podSecurityContext.fsGroup` | Set Node exporter pod's Security Context fsGroup | `1001` |\n| `containerSecurityContext.enabled` | Enabled containers' Security Context | `true` |\n| `containerSecurityContext.seLinuxOptions` | Set SELinux options in container | `{}` |\n| `containerSecurityContext.runAsUser` | Set containers' Security Context runAsUser | `1001` \n\n_Note: the README for this chart is longer than the DockerHub length limit of 25000, so it has been trimmed. The full README can be found at https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-app-doc/apps-charts-node-exporter-index.html_","has_starred","hub_user","immutable_tags_settings",{"_110":11,"_111":112},"enabled","rules",[113],".*","is_automated","permissions",{"_117":21,"_118":11,"_119":11},"read","write","admin","user","storage_size",4341558,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","","tagAttestations","displaySecurityMetadata","showSbxLogoOverride","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_27":28,"_63":-7,"_61":-7,"_62":-7,"_29":135,"_35":36,"_137":-7,"_138":11},{"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":136,"_43":44,"_45":34,"_46":47,"_48":49,"_50":51,"_52":53,"_54":-5,"_55":44,"_56":57,"_58":21},[],"imageWithLayers","hasPermissionToViewRepoSettings","actionData","errors"]

bitnamicharts/node-exporter:sha256-b188a739cd7fadb587ff2e481ea1a66e8fb9563cbf7466e4d63b07e322628535