[{"_1":2,"_129":-5,"_130":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_123":124},"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,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)",{"_23":24,"_25":26,"_55":56,"_57":-7,"_58":-7,"_59":-7,"_60":-7,"_61":-5,"_62":-5,"_63":11,"_64":11,"_48":65,"_115":17,"_83":84,"_116":82,"_117":47,"_31":32,"_118":11,"_119":17,"_120":74,"_121":-5,"_122":11},"scanningType","none","tagData",{"_27":28,"_29":30,"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":30,"_42":43,"_44":45,"_46":47,"_48":49,"_50":-5,"_51":40,"_52":53,"_54":17},"content_type","image","creator",35095401,"digest","sha256:7149fd14e9ccf57d0166b57914e50492d08dd5460b0d36a43f6c1aae691a4167","full_size",7947,"id",953560502,"images",[],"last_updated","2025-08-13T17:36:16.917252Z","last_updater","last_updater_username","bitnamibot508","media_type","application/vnd.oci.image.index.v1+json","name","sha256-a09df5e33b17c6aa5ec96a78113d7124555192398157c8684bd24235ccbd1e37","repository",27257850,"tag_last_pulled","tag_last_pushed","tag_status","inactive","v2","tagImages",[],"layerOrdinals","packageName","cveId","sbom","scoutSummary","staticSummary","isScoutPaymentRequired","canSeeVulnerabilities",{"_66":67,"_68":69,"_71":72,"_73":74,"_75":11,"_39":76,"_77":78,"_79":80,"_46":82,"_83":84,"_85":86,"_87":-5,"_88":89,"_90":91,"_92":93,"_94":-5,"_95":89,"_96":97,"_98":11,"_99":84,"_100":101,"_106":11,"_107":108,"_112":84,"_113":114},"categories",[],"content_types",[70,28],"helm","date_registered","2025-05-02T19:16:30.462214Z","description","","is_private","2025-08-19T23:59:22.189853Z","last_modified","2026-03-16T14:23:30.1494Z","media_types",[81,45],"application/vnd.cncf.helm.config.v1+json","envoy-gateway","namespace","bitnamicharts","pull_count",307242,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","\n\n# Bitnami Secure Images Helm chart for Envoy Gateway\n\nEnvoy Gateway simplifies traffic management by extending Envoy Proxy's features, offering Kubernetes Gateway API integration for secure, scalable, and observable application routing\n\n[Overview of Envoy Gateway](https://gateway.envoyproxy.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/envoy-gateway\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 [Envoy Gateway](https://github.com/bitnami/containers/tree/main/bitnami/envoy-gateway) 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 REGISTRY_NAME/REPOSITORY_NAME/envoy-gateway\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 Envoy Gateway 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### Operator configuration\n\nThe Bitnami Envoy Gateway chart allows [configuring the operator](https://gateway.envoyproxy.io/docs/api/extension_types/#envoygateway) using ConfigMaps. This is done using the `overrideConfiguration` parameter, which merges the provided settings with the default configuration. In the example below we add extra configuration parameters to the operator:\n\n```yaml\noverrideConfiguration:\n admin:\n enableDumpConfig: false\n```\n\nIt is also possible to use an existing ConfigMap using the `existingConfigMap` parameter (note that this is not compatible with the `overrideConfiguration` parameter).\n\n### Certificate Generation Job\n\nThe chart provides a certificate generation job, which uses the Envoy Operator `certgen` command provide to create all the necessary TLS secrets. This is enabled by setting `certgen.enabled=true` and all the Job settings can be configured under the `certgen` section.\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### Prometheus metrics\n\nThis chart can be integrated with Prometheus by setting `metrics.enabled` to true. This will expose the envoy-gateway native Prometheus endpoint in both the container and 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### [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### Additional environment variables\n\nIn case you want to add extra environment variables (useful for advanced operations like custom init scripts), you can use the `extraEnvVars` property:\n\n```yaml\nextraEnvVars:\n - name: LOG_LEVEL\n value: error\n```\n\nAlternatively, you can use a ConfigMap or a Secret with the environment variables. To do so, use the `extraEnvVarsCM` or the `extraEnvVarsSecret` values inside the `operator`, `apiserver` and `cluster` sections.\n\n### Sidecars\n\nIf additional containers are needed in the same pod as envoy-gateway (such as additional metrics or logging exporters), they can be defined using the `sidecars` parameter:\n\n```yaml\nsidecars:\n- name: your-image-name\n image: your-image\n imagePullPolicy: Always\n ports:\n - name: portname\n containerPort: 1234\n```\n\nIf these sidecars export extra ports, extra port definitions can be added using the `service.extraPorts` parameter (where available), as shown in the example below:\n\n```yaml\nservice:\n extraPorts:\n - name: extraPort\n port: 11311\n targetPort: 11311\n```\n\nIf additional init containers are needed in the same pod, they can be defined using the `initContainers` parameter. Here is an example:\n\n```yaml\ninitContainers:\n - name: your-image-name\n image: your-image\n imagePullPolicy: Always\n ports:\n - name: portname\n containerPort: 1234\n```\n\nLearn more about [sidecar containers](https://kubernetes.io/docs/concepts/workloads/pods/) and [init containers](https://kubernetes.io/docs/concepts/workloads/pods/init-containers/).\n\n### Deploying extra resources\n\nApart from the Operator, you may want to deploy Gateway, HTTPRoutes or other operator objects. For covering this case, the chart allows adding the full specification of other objects using the `extraDeploy` parameter. The following example deploys a GatewayClasse, a Gateway, HTTPRoutes and a service (adapted from the upstream [quickstart](https://gateway.envoyproxy.io/latest/tasks/quickstart/) documentation):\n\n```yaml\nextraDeploy:\n- apiVersion: gateway.networking.k8s.io/v1\n kind: GatewayClass\n metadata:\n name: eg\n spec:\n controllerName: gateway.envoyproxy.io/gatewayclass-controller\n- apiVersion: gateway.networking.k8s.io/v1\n kind: Gateway\n metadata:\n name: eg\n spec:\n gatewayClassName: eg\n listeners:\n - name: http\n protocol: HTTP\n port: 80\n- apiVersion: v1\n kind: ServiceAccount\n metadata:\n name: backend\n- apiVersion: v1\n kind: Service\n metadata:\n name: backend\n labels:\n app: backend\n service: backend\n spec:\n ports:\n - name: http\n port: 80\n targetPort: 8080\n selector:\n app: backend\n- apiVersion: apps/v1\n kind: Deployment\n metadata:\n name: backend\n spec:\n replicas: 1\n selector:\n matchLabels:\n app: backend\n version: v1\n template:\n metadata:\n labels:\n app: backend\n version: v1\n spec:\n serviceAccountName: backend\n containers:\n - image: bitnami/nginx\n imagePullPolicy: Always\n name: backend\n ports:\n - containerPort: 8080\n- apiVersion: gateway.networking.k8s.io/v1\n kind: HTTPRoute\n metadata:\n name: backend\n spec:\n parentRefs:\n - name: eg\n hostnames:\n - \"www.example.com\"\n rules:\n - backendRefs:\n - group: \"\"\n kind: Service\n name: backend\n port: 80\n weight: 1\n matches:\n - path:\n type: PathPrefix\n value: /\n```\n\nCheck the [Envoy Gateway official documentation](https://envoy-gateway.io/documentation/current/) for the list of available objects.\n\n### Pod affinity\n\nThis chart allows you to set your custom affinity using the `affinity` parameter. 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, use one 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### 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` | Override Kubernetes version | `\"\"` |\n| `apiVersions` | Override Kubernetes API versions reported by .Capabilities | `[]` |\n| `nameOverride` | String to partially override common.names.name | `\"\"` |\n| `fullnameOverride` | String to fully override common.names.fullname | `\"\"` |\n| `namespaceOverride` | String to fully override common.names.namespace | `\"\"` |\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| `commonLabels` | Labels to add to all deployed objects | `{}` |\n| `commonAnnotations` | Annotations to add to all deployed objects | `{}` |\n| `clusterDomain` | Kubernetes cluster domain name | `cluster.local` |\n| `extraDeploy` | Array of extra objects to deploy with the release | `[]` |\n\n### Envoy Gateway parameters\n\n| Name | Description | Value |\n| --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |\n| `image.registry` | Envoy Gateway image registry | `REGISTRY_NAME` |\n| `image.repository` | Envoy Gateway image repository | `REPOSITORY_NAME/envoy-gateway` |\n| `image.digest` | Envoy Gateway image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag image tag (immutable tags are recommended) | `\"\"` |\n| `image.pullPolicy` | Envoy Gateway image pull policy | `IfNotPresent` |\n| `image.pullSecrets` | Envoy Gateway image pull secrets | `[]` |\n| `ratelimitImage.registry` | Envoy Rate Limit image registry | `REGISTRY_NAME` |\n| `ratelimitImage.repository` | Envoy Rate Limit image repository | `REPOSITORY_NAME/envoy-ratelimit` |\n| `ratelimitImage.digest` | Envoy Rate Limit image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `\"\"` |\n| `ratelimitImage.pullPolicy` | Rate Limit image pull policy | `IfNotPresent` |\n| `ratelimitImage.fips.openssl` | Configure OpenSSL FIPS mode: '', 'restricted', 'relaxed', 'off'. If empty (\"\"), 'global.defaultFips' would be used | `\"\"` |\n| `ratelimitImage.fips.golang` | Configure Golang FIPS mode: '', 'restricted', 'relaxed', 'off'. If empty (\"\"), 'global.defaultFips' would be used | `restricted` |\n| `envoyImage.registry` | Envoy image registry | `REGISTRY_NAME` |\n| `envoyImage.repository` | Envoy image repository | `REPOSITORY_NAME/envoy` |\n| `envoyImage.digest` | Envoy image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `\"\"` |\n| `replicaCount` | Number of Envoy Gateway replicas to deploy | `1` |\n| `livenessProbe.enabled` | Enable livenessProbe on Envoy Gateway containers | `true` |\n| `livenessProbe.initialDelaySeconds` | Initial delay seconds for livenessProbe | `5` |\n| `livenessProbe.periodSeconds` | Period seconds for livenessProbe | `10` |\n| `livenessProbe.timeoutSeconds` | Timeout seconds for livenessProbe | `5` |\n| `livenessProbe.failureThreshold` | Failure threshold for livenessProbe | `5` |\n| `livenessProbe.successThreshold` | Success threshold for livenessProbe | `1` |\n| `readinessProbe.enabled` | Enable readinessProbe on Envoy Gateway containers | `true` |\n| `readinessProbe.initialDelaySeconds` | Initial delay seconds for readinessProbe | `5` |\n| `readinessProbe.periodSeconds` | Period seconds for readinessProbe \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-envoy-gateway-index.html_","has_starred","hub_user","immutable_tags_settings",{"_102":11,"_103":104},"enabled","rules",[105],".*","is_automated","permissions",{"_109":17,"_110":11,"_111":11},"read","write","admin","user","storage_size",11297721,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","tagAttestations","displaySecurityMetadata","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_23":24,"_59":-7,"_57":-7,"_58":-7,"_25":125,"_31":32,"_127":-7,"_128":11},{"_27":28,"_29":30,"_31":32,"_33":34,"_35":36,"_37":126,"_39":40,"_41":30,"_42":43,"_44":45,"_46":47,"_48":49,"_50":-5,"_51":40,"_52":53,"_54":17},[],"imageWithLayers","hasPermissionToViewRepoSettings","actionData","errors"]

bitnamicharts/envoy-gateway:sha256-a09df5e33b17c6aa5ec96a78113d7124555192398157c8684bd24235ccbd1e37