bitnamicharts/node-exporter
bitnamicharts
Bitnami提供的Helm chart，用于在Kubernetes环境中部署Node Exporter，以收集主机系统的硬件和操作系统指标。
下载次数: 0状态：社区镜像维护者：bitnamicharts仓库类型：镜像最近更新：11 个月前
让 AI 帮你使用轩辕镜像？ · 展开查看说明 · 点击收起说明
如果你使用 DeepSeek、元宝 AI、Copilot、ChatGPT 等 AI 工具，协助配置轩辕镜像、编写 docker pull 命令、修改 Docker Compose 镜像地址、配置镜像加速、排查镜像拉取失败、分析报错日志等问题，请先让 AI 阅读并遵守轩辕镜像的规则文档。
只需在 AI 对话中先发送下面这句话即可：
请先完整阅读并严格遵守以下文档中的全部规则与要求：
https://xuanyuan.cloud/agents.md
在未充分阅读并理解该文档前，不要生成任何命令、配置、修改建议、故障排查方案或技术回答。后续所有输出都必须严格以该文档中的规范为最高优先级执行。查看 agents.md 用法指南与完整示范。国内用户首推 元宝 AI、DeepSeek 的深度思考模式，不推荐豆包 AI；Cursor 等编辑器可在对话 @ 该链接，或加入 User Rules。 若 AI 无法访问外链，可 打开说明文档 复制全文粘贴。文档会随站点更新，复制内容可能过期，建议定期检查。
Bitnami Secure Images Helm chart for Node Exporter
Prometheus exporter for hardware and OS metrics exposed by UNIX kernels, with pluggable metric collectors.
https://prometheus.io/
Trademarks: 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.
TL;DR
consolehelm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/node-exporter
Note: You need to substitute the placeholders
REGISTRY_NAMEandREPOSITORY_NAMEwith a reference to your Helm chart registry and repository.
Introduction
This chart bootstraps https://github.com/bitnami/containers/tree/main/bitnami/node-exporter on https://kubernetes.io using the https://helm.sh package manager.
Before you begin
- Kubernetes 1.23+
- Helm 3.8.0+
Installing the Chart
To install the chart with the release name my-release:
consolehelm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/node-exporter
Note: You need to substitute the placeholders
REGISTRY_NAMEandREPOSITORY_NAMEwith a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to useREGISTRY_NAME=registry-1.docker.ioandREPOSITORY_NAME=bitnamicharts.
The command deploys Node Exporter on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.
Configuration and installation details
This section describes credentials, configuration, and other installation options.
Resource requests and limits
Bitnami 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.
To make this process easier, the chart contains the resourcesPreset values, which automatically sets the resources section according to different presets. Check these presets in 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 https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/.
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
It 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.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
Backup and restore
To 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 https://velero.io/, a Kubernetes backup/restore tool. Find the instructions for using Velero in 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.
FIPS parameters
The FIPS parameters only have effect if you are using images from the https://go-vmware.broadcom.com/contact-us.
For more information on this new support, please refer to the https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/security-frameworks-FIPS-compliance.html.
Set Pod affinity
This chart allows you to set custom Pod affinity using the affinity parameter(s). Find more information about Pod affinity in the https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity.
As an alternative, you can use the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the https://github.com/bitnami/charts/tree/main/bitnami/common#affinities chart. To do so, set the podAffinityPreset, podAntiAffinityPreset, or nodeAffinityPreset parameters.
Resource Type
This 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.
Installing 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.
Parameters
The following subsections list global, common, and component-specific parameters.
Global parameters
| Name | Description | Value |
|---|---|---|
global.imageRegistry | Global Docker image registry | "" |
global.imagePullSecrets | Global Docker registry secret names as an array | [] |
global.defaultStorageClass | Global default StorageClass for Persistent Volume(s) | "" |
global.storageClass | DEPRECATED: use global.defaultStorageClass instead | "" |
global.defaultFips | Default value for the FIPS configuration (allowed values: '', restricted, relaxed, off). Can be overridden by the 'fips' object | restricted |
global.security.allowInsecureImages | Allows skipping image verification | false |
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 |
Common parameters
| Name | Description | Value |
|---|---|---|
kubeVersion | Force target Kubernetes version (using Helm capabilities if not set) | "" |
nameOverride | String to partially override common.names.fullname template (will maintain the release name) | "" |
fullnameOverride | String to fully override common.names.fullname template with a string | "" |
namespaceOverride | String to fully override common.names.namespace | "" |
commonAnnotations | Annotations to add to all deployed objects | {} |
commonLabels | Labels to add to all deployed objects | {} |
extraDeploy | Array of extra objects to deploy with the release | [] |
clusterDomain | Kubernetes cluster domain name | cluster.local |
diagnosticMode.enabled | Enable diagnostic mode (all probes will be disabled and the command will be overridden) | false |
diagnosticMode.command | Command to override all containers in the the deployment(s)/statefulset(s) | ["sleep"] |
diagnosticMode.args | Args to override all containers in the the deployment(s)/statefulset(s) | ["infinity"] |
Node Exporter parameters
| Name | Description | Value |
|---|---|---|
resourceType | Specify how to deploy Node Exporter (allowed values: daemonset and deployment) | daemonset |
replicaCount | Number of replicas to deploy (when resourceType is deployment) | 1 |
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 |
automountServiceAccountToken | Mount Service Account token in pod | false |
hostAliases | Deployment pod host aliases | [] |
runtimeClassName | Name of the runtime class to be used by pod(s) | "" |
rbac.create | Whether to create and use RBAC resources or not | true |
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 |
rbac.rules | Custom RBAC rules to set | [] |
serviceAccount.create | Specifies whether a ServiceAccount should be created | true |
serviceAccount.name | Name of the service account to use. If not set and create is true, a name is generated using the fullname template. | "" |
serviceAccount.automountServiceAccountToken | Automount service account token for the server service account | false |
serviceAccount.annotations | Annotations for service account. Evaluated as a template. Only used if create is true. | {} |
image.registry | Node Exporter image registry | REGISTRY_NAME |
image.repository | Node Exporter image repository | REPOSITORY_NAME/node-exporter |
image.digest | Node Exporter image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | "" |
image.pullPolicy | Node Exporter image pull policy | IfNotPresent |
image.pullSecrets | Specify docker-registry secret names as an array | [] |
containerPorts.metrics | Node Exporter container port | 9100 |
sidecars | Add additional sidecar containers to the Node exporter pod(s) | [] |
initContainers | Add additional init containers to the Node exporter pod(s) | [] |
pdb.create | Enable/disable a Pod Disruption Budget creation | true |
pdb.minAvailable | Minimum number/percentage of pods that should remain scheduled | "" |
pdb.maxUnavailable | Maximum number/percentage of pods that may be made unavailable. Defaults to 1 if both pdb.minAvailable and pdb.maxUnavailable are empty. | "" |
extraArgs | Additional command line arguments to pass to node-exporter | {} |
command | Override default container command (useful when using custom images) | [] |
args | Override default container args (useful when using custom images) | [] |
lifecycleHooks | for the Node exporter container(s) to automate configuration before or after startup | {} |
extraEnvVars | Array with extra environment variables to add to Node exporter container | [] |
extraEnvVarsCM | Name of existing ConfigMap containing extra env vars for Node exporter container | "" |
extraEnvVarsSecret | Name of existing Secret containing extra env vars for Node exporter container | "" |
extraVolumes | Additional volumes to the node-exporter pods | [] |
extraVolumeMounts | Additional volumeMounts to the node-exporter container | [] |
podSecurityContext.enabled | Enabled Node exporter pods' Security Context | true |
podSecurityContext.fsGroupChangePolicy | Set filesystem group change policy | Always |
podSecurityContext.sysctls | Set kernel settings using the sysctl interface | [] |
podSecurityContext.supplementalGroups | Set filesystem extra groups | [] |
podSecurityContext.fsGroup | Set Node exporter pod's Security Context fsGroup | 1001 |
containerSecurityContext.enabled | Enabled containers' Security Context | true |
containerSecurityContext.seLinuxOptions | Set SELinux options in container | {} |
containerSecurityContext.runAsUser | Set containers' Security Context runAsUser | 1001 |
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
镜像拉取方式
您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本，请访问 标签列表页面。
轩辕镜像加速拉取命令点我查看更多 node-exporter 镜像标签
docker pull docker.xuanyuan.run/bitnamicharts/node-exporter:<标签>
DockerHub 原生拉取命令
docker pull bitnamicharts/node-exporter:<标签>
镜像拉取常见问题
功能
错误码
用户好评
来自真实用户的反馈，见证轩辕镜像的优质服务
oldzhang
运维工程师
Linux服务器
5
"Docker访问体验非常流畅，大镜像也能快速完成下载。"