You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(chart): Allow configuring envoy proxy image via helm chart (#8785)
* feat: Allow configuring envoy proxy defaults via helm chart
This commit is a continuation of the previous work to support supplying default proxy settings added in #7698 and adds three new chart values under `global.images.envoyProxy`:
| Value | Type | Default | Description |
|----------------------------------------|--------|------|---------------------------------------------------------------------|
| `global.images.envoyProxy.image` | string | `""` | Full image name (`registry/repo:tag`) for the Envoy Proxy container |
| `global.images.envoyProxy.pullPolicy` | string | `""` | Image pull policy |
| `global.images.envoyProxy.pullSecrets` | list | `[]` | Image pull secrets |
When any of these are set, the chart generates an `envoyProxy:` block inside the `EnvoyGateway` ConfigMap, wiring into the existing `EnvoyGatewaySpec.envoyProxy` field (added in #7698). The global `imageRegistry` override takes highest precedence, consistent with other chart components.
Full EnvoyProxy defaults (replicas, resources, etc.) can be provided via `config.envoyGateway.envoyProxy`; the image values are merged on top.
Closes#4764.
Signed-off-by: Michael Sommerville <msommerville@gmail.com>
(cherry picked from commit 8570285)
Copy file name to clipboardExpand all lines: release-notes/current.yaml
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,7 @@ security updates: |
10
10
Bump Envoy ratelimit image to `05c08d03`.
11
11
# New features or capabilities added in this release.
12
12
new features: |
13
+
Added support for defining Envoy Proxy image, pullPolicy, and pullSecrets via the helm chart. Note that to merge these helm-configured values with EnvoyProxy resources, the EnvoyProxy must include `mergeType: StrategicMerge` or `mergeType: JSONMerge`.
13
14
14
15
bug fixes: |
15
16
Rejected ClientTrafficPolicy if invalid TLS cipher suites are configured.
0 commit comments