[{"_1":2,"_133":-5,"_134":-5},"loaderData",{"_3":4,"_13":14,"_20":21,"_127":128},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)",{"_22":23,"_24":25,"_54":55,"_56":-7,"_57":-7,"_58":-7,"_59":-7,"_60":-5,"_61":-5,"_62":11,"_63":11,"_47":64,"_118":17,"_86":87,"_119":85,"_120":46,"_30":31,"_121":11,"_122":17,"_123":124,"_125":-5,"_126":11},"scanningType","none","tagData",{"_26":27,"_28":29,"_30":31,"_32":33,"_34":35,"_36":37,"_38":39,"_40":29,"_41":42,"_43":44,"_45":46,"_47":48,"_49":-5,"_50":39,"_51":52,"_53":17},"content_type","image","creator",35095401,"digest","sha256:de06a300f27639af6d8cb1a7fa4780aa98bba491b1bba2ae5e2104c231fd4496","full_size",7947,"id",922508872,"images",[],"last_updated","2025-06-24T14:15:29.996232Z","last_updater","last_updater_username","bitnamibot508","media_type","application/vnd.oci.image.index.v1+json","name","sha256-e75d5e3f6e38afd6ecb5807a93e32e9e9fdec2287c31592b792bb6fb92fe9331","repository",27060649,"tag_last_pulled","tag_last_pushed","tag_status","inactive","v2","tagImages",[],"layerOrdinals","packageName","cveId","sbom","scoutSummary","staticSummary","isScoutPaymentRequired","canSeeVulnerabilities",{"_65":66,"_71":72,"_74":75,"_76":77,"_78":11,"_38":79,"_80":81,"_82":83,"_45":85,"_86":87,"_88":89,"_90":-5,"_91":92,"_93":94,"_95":96,"_97":-5,"_98":92,"_99":100,"_101":11,"_102":87,"_103":104,"_109":11,"_110":111,"_115":87,"_116":117},"categories",[67],{"_45":68,"_69":70},"Monitoring & observability","slug","monitoring-and-observability","content_types",[73,27],"helm","date_registered","2025-04-15T14:29:53.759173Z","description","Bitnami Premium image for cAdvisor","is_private","2025-08-13T16:21:15.932835Z","last_modified","2026-03-16T14:23:10.980549Z","media_types",[84,44],"application/vnd.cncf.helm.config.v1+json","cadvisor","namespace","bitnamicharts","pull_count",186180,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","\n\n# Bitnami Secure Images Helm chart for cAdvisor\n\ncAdvisor (Container Advisor) is an open-source tool by Google for monitoring containers, collecting metrics like CPU, memory, and network usage.\n\n[Overview of cAdvisor](https://github.com/google/cadvisor)\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/cadvisor\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 a [cAdvisor](https://github.com/bitnami/containers/tree/main/bitnami/cadvisor) deployment on a [Kubernetes](https://kubernetes.io) cluster 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/cadvisor\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 cAdvisor on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.\n\n> **Tip**: List all releases using `helm list`\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### Image\n\nThe `image` parameter allows specifying which image will be pulled for the chart.\n\n#### Private registry\n\nIf you configure the `image` value to one in a private registry, you will need to [specify an image pull secret](https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod).\n\n1. Manually create image pull secret(s) in the namespace. See [this YAML example reference](https://kubernetes.io/docs/concepts/containers/images/#creating-a-secret-with-a-docker-config). Consult your image registry's documentation about getting the appropriate secret.\n2. Note that the `imagePullSecrets` configuration value cannot currently be passed to helm using the `--set` parameter, so you must supply these using a `values.yaml` file, such as:\n\n ```yaml\n imagePullSecrets:\n - name: SECRET_NAME\n ```\n\n3. Install the chart\n\n### Setting Pod's affinity\n\nThis chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod's 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 of 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### Prometheus metrics\n\nThis chart can be integrated with Prometheus by setting `metrics.enabled` to `true`. This will expose cAdvisor native Prometheus endpoint in the service. It will have the necessary annotations to be automatically scraped by Prometheus.\n\n#### Prometheus requirements\n\nIt is necessary to have a working installation of Prometheus or Prometheus Operator for the integration to work. Install the [Bitnami Prometheus helm chart](https://github.com/bitnami/charts/tree/main/bitnami/prometheus) or the [Bitnami Kube Prometheus helm chart](https://github.com/bitnami/charts/tree/main/bitnami/kube-prometheus) to easily have a working Prometheus in your cluster.\n\n#### Integration with Prometheus Operator\n\nThe chart can deploy `ServiceMonitor` objects for integration with Prometheus Operator installations. To do so, set the value `metrics.serviceMonitor.enabled=true`. Ensure that the Prometheus Operator `CustomResourceDefinitions` are installed in the cluster or it will fail with the following error:\n\n```text\nno matches for kind \"ServiceMonitor\" in version \"monitoring.coreos.com/v1\"\n```\n\nInstall the [Bitnami Kube Prometheus helm chart](https://github.com/bitnami/charts/tree/main/bitnami/kube-prometheus) for having the necessary CRDs and the Prometheus Operator.\n\n### Extra cAdvisor parameters\n\nIt is possible to add extra configuration parameters to the `cadvisor` command using the `extraArgs` value. In the following example we use add the extra `log_cadvisor_usage=true` argument:\n\n```yaml\nextraArgs:\n - -log_cadvisor_usage=true\n```\n\nCheck the [official cAdvisor documentation](https://github.com/google/cadvisor/blob/master/docs/runtime_options.md#L1) for the list of available arguments.\n\n### Hostpath mounts\n\nThe Bitnami cAdvisor chart mounts a set of host folders by default, which can be enabled/disabled with the following values inside the the `defaultMounts` section:\n\n- `defaultMounts.rootfs`: Mount the host `/` folder\n- `defaultMounts.varRun`: Mount the host `/var/run` folder\n- `defaultMounts.sys`: Mount the host `/sys` folder\n- `defaultMounts.varLibDocker`: Mount the host `/var/lib/docker` folder\n- `defaultMounts.devDisk`: Mount the host `/dev/disk` folder\n\nYou can mount extra folders using the `extraVolumes` and `extraVolumeMounts` values.\n\n### Gateway API\n\nThis chart provides support for exposing cAdvisor using the [Gateway API](https://gateway-api.sigs.k8s.io/) and its `HTTPRoute` resource. If you have a Gateway controller installed on your cluster, such as APISIX, Contour, Envoy Gateway, NGINX Gateway Fabric or Kong Ingress Controller you can utilize the Gateway controller to serve your application. To enable Gateway API integration, set `httpRoute.enabled` to `true`.\nThe Gateway to be used can be customized by setting the `httpRoute.parentRefs` parameter. By default, it will reference a Gateway named `gateway` in the same namespace as the release.\n\nYou can specify the list of hostnames to be mapped to the deployment using the `httpRoute.hostnames` parameter. Additionally, you can customize the rules used to route the traffic to the service by modifying the `httpRoute.matches` and `httpRoute.filters` parameters or adding new rules using the `httpRoute.extraRules` parameter.\n\n### Ingress\n\nThis chart provides support for Ingress resources. If you have an ingress controller installed on your cluster, such as [nginx-ingress-controller](https://github.com/bitnami/charts/tree/main/bitnami/nginx-ingress-controller) or [contour](https://github.com/bitnami/charts/tree/main/bitnami/contour) you can utilize the ingress controller to serve your application. To enable Ingress integration, set `ingress.enabled` to `true`.\n\nThe most common scenario is to have one host name mapped to the deployment. In this case, the `ingress.hostname` property can be used to set the host name. The `ingress.tls` parameter can be used to add the TLS configuration for this host.\n\nHowever, it is also possible to have more than one host. To facilitate this, the `ingress.extraHosts` parameter (if available) can be set with the host names specified as an array. The `ingress.extraTLS` parameter (if available) can also be used to add the TLS configuration for extra hosts.\n\n> NOTE: For each host specified in the `ingress.extraHosts` parameter, it is necessary to set a name, path, and any annotations that the Ingress controller should know about. Not all annotations are supported by all Ingress controllers, but [this annotation reference document](https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/nginx-configuration/annotations.md) lists the annotations supported by many popular Ingress controllers.\n\nAdding the TLS parameter (where available) will cause the chart to generate HTTPS URLs, and the application will be available on port 443. The actual TLS secrets do not have to be generated by this chart. However, if TLS is enabled, the Ingress record will not work until the TLS secret exists.\n\n[Learn more about Ingress controllers](https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/).\n\n### Configure TLS Secrets for use with Ingress\n\nThis chart facilitates the creation of TLS secrets for use with the Ingress controller (although this is not mandatory). There are several common use cases:\n\n- Generate certificate secrets based on chart parameters.\n- Enable externally generated certificates.\n- Manage application certificates via an external service (like [cert-manager](https://github.com/jetstack/cert-manager/)).\n- Create self-signed certificates within the chart (if supported).\n\nIn the first two cases, a certificate and a key are needed. Files are expected in `.pem` format.\n\nHere is an example of a certificate file:\n\n> NOTE: There may be more than one certificate if there is a certificate chain.\n\n```text\n-----BEGIN CERTIFICATE-----\nMIID6TCCAtGgAwIBAgIJAIaCwivkeB5EMA0GCSqGSIb3DQEBCwUAMFYxCzAJBgNV\n...\njScrvkiBO65F46KioCL9h5tDvomdU1aqpI/CBzhvZn1c0ZTf87tGQR8NK7v7\n-----END CERTIFICATE-----\n```\n\nHere is an example of a certificate key:\n\n```text\n-----BEGIN RSA PRIVATE KEY-----\nMIIEogIBAAKCAQEAvLYcyu8f3skuRyUgeeNpeDvYBCDcgq+LsWap6zbX5f8oLqp4\n...\nwrj2wDbCDCFmfqnSJ+dKI3vFLlEz44sAV8jX/kd4Y6ZTQhlLbYc=\n-----END RSA PRIVATE KEY-----\n```\n\n- If using Helm to manage the certificates based on the parameters, copy these values into the `certificate` and `key` values for a given `*.ingress.secrets` entry.\n- If managing TLS secrets separately, it is necessary to create a TLS secret with name `INGRESS_HOSTNAME-tls` (where INGRESS_HOSTNAME is a placeholder to be replaced with the hostname you set using the `*.ingress.hostname` parameter).\n- If your cluster has a [cert-manager](https://github.com/jetstack/cert-manager) add-on to automate the management and issuance of TLS certificates, add to `*.ingress.annotations` the [corresponding ones](https://cert-manager.io/docs/usage/ingress/#supported-annotations) for cert-manager.\n- If using self-signed certificates created by Helm, set both `*.ingress.tls` and `*.ingress.selfSigned` to `true`.\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## 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.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 cadvisor.fullname template (will maintain the release name) | `\"\"` |\n| `fullnameOverride` | String to fully override cadvisor.fullname template | `\"\"` |\n| `namespaceOverride` | String to fully override common.names.namespace | `\"\"` |\n| `clusterDomain` | Kubernetes cluster domain name | `cluster.local` |\n| `commonAnnotations` | Common annotations to add to all cAdvisor resources (sub-charts are not considered). Evaluated as a template | `{}` |\n| `commonLabels` | Common labels to add to all cAdvisor resources (sub-charts are not considered). Evaluated as a template | `{}` |\n| `extraDeploy` | Array of extra objects to deploy with the release (evaluated as a template). | `[]` |\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 deployment | `[\"sleep\"]` |\n| `diagnosticMode.args` | Args to override all containers in the deployment | `[\"infinity\"]` |\n\n### cAdvisor parameters\n\n| Name | Description | Value |\n| --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------- |\n| `image.registry` | cAdvisor image registry | `REGISTRY_NAME` |\n| `image.repository` | cAdvisor Image name | `REPOSITORY_NAME/cadvisor` |\n| `image.digest` | cAdvisor image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `\"\"` |\n| `image.pullPolicy` | cAdvisor image pull policy | `IfNotPresent` |\n| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |\n| `command` | Override default container command (useful when using custom images) | `[]` |\n| `args` | Override default container args (useful when using custom images) | `[]` |\n| `extraArgs` | Add extra arguments to the default command | `[]` |\n| `updateStrategy.type` | Set up update strategy. | `RollingUpdate` |\n| `priorityClassName` | cAdvisor pods' priorityClassName | `\"\"` |\n| `schedulerName` | Name of the k8s scheduler (other than default) | `\"\"` |\n| `runtimeClassName` | Name of the runtime class to be used by pod(s) | `\"\"` |\n| `topologySpreadConstraints` | Topology Spread Constraints for pod assignment | `[]` |\n| `automountServiceAccountToken` | Mount Service Account token in pod | `false` |\n| `hostAliases` | Add daemonset host aliases | `[]` |\n| `extraEnvVars` | Extra environment variables | `[]` |\n| `extraEnvVarsCM` | ConfigMap containing extra env vars | `\"\"` |\n| `extraEnvVarsSecret` | Secret containing extra env vars (in case of sensitive data) | `\"\"` |\n| `defaultMounts.rootfs` | Mount host / \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-cadvisor-index.html_","has_starred","hub_user","immutable_tags_settings",{"_105":11,"_106":107},"enabled","rules",[108],".*","is_automated","permissions",{"_112":17,"_113":11,"_114":11},"read","write","admin","user","storage_size",614955,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","","tagAttestations","displaySecurityMetadata","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_22":23,"_58":-7,"_56":-7,"_57":-7,"_24":129,"_30":31,"_131":-7,"_132":11},{"_26":27,"_28":29,"_30":31,"_32":33,"_34":35,"_36":130,"_38":39,"_40":29,"_41":42,"_43":44,"_45":46,"_47":48,"_49":-5,"_50":39,"_51":52,"_53":17},[],"imageWithLayers","hasPermissionToViewRepoSettings","actionData","errors"]

bitnamicharts/cadvisor:sha256-e75d5e3f6e38afd6ecb5807a93e32e9e9fdec2287c31592b792bb6fb92fe9331