3 # If set, these take highest precedence and change envoyGateway, envoyProxy, and ratelimit's container registry and pull secrets.
4 # -- Global override for image registry
6 # -- Global override for image pull secrets
8 # If set, these override image-specific values: useful when installing the chart in a private registry environment.
9 # Override image-specific values directly if a global override is not desired.
12 # -- Full image for the Envoy Gateway control plane Deployment installed by this chart.
13 image: cgr.dev/scratch-images/test-tmp/envoy-gateway:1.8.4-r2@sha256:fa29f41f1f990522ed81d1e328a4eaf362965063559a5253b359d99811003435
14 # -- Image pull policy for the Envoy Gateway control plane Deployment.
15 # Default behavior: latest images will be Always else IfNotPresent.
16 pullPolicy: IfNotPresent
17 # -- Pull secrets for the Envoy Gateway control plane Deployment.
20 # This is the full image name including the hub, repo, and tag.
21 image: cgr.dev/scratch-images/test-tmp/envoy-ratelimit:1.8.4-r2@sha256:1e1fbf048845d62886b25747610d889bc8cd81ca0a58568d44f4d2b94e1453d3
22 # Specify image pull policy if default behavior isn't desired.
23 # Default behavior: latest images will be Always else IfNotPresent.
24 pullPolicy: IfNotPresent
25 # List of secrets in the same namespace of the component that can be used to pull images from private repositories.
28 # -- Full image for the managed Envoy Proxy data plane.
29 # This updates the generated `envoyProxy` config and does not change the `envoy-gateway`
30 # control plane Deployment image. If not specified, the default image built into
31 # `envoy-gateway` is used.
32 image: cgr.dev/scratch-images/test-tmp/envoy:distroless-v1.38.4-r0@sha256:f0919d2298a4222f1a4ce256f5c2f346b66340efab7a13284e7a1a2c2044c840
33 # -- Image pull policy for the managed Envoy Proxy data plane.
34 # Default behavior: IfNotPresent.
36 # -- Pull secrets for the managed Envoy Proxy data plane.
38# Values for CRDs dependency
40 # -- Install Envoy Gateway CRDs, Gateway API CRDs, and Gateway API safe upgrade policy resources. Set to false when these resources are managed separately.
42# -- Labels to apply to all resources
47 # unhealthyPodEvictionPolicy: IfHealthyBudget
52 # if both this and global.imageRegistry are specified, this has to include both registry and repository explicitly, eg docker.io/envoyproxy/gateway
57 # -- Additional environment variables for the envoy-gateway container.
66 allowPrivilegeEscalation: false
71 readOnlyRootFilesystem: true
77 # -- Volume source for the Wasm module cache mounted at /var/lib/eg/wasm. Defaults to an emptyDir when left empty.
78 # Example: persist the Wasm module cache across controller restarts by backing it with a PersistentVolumeClaim:
80 # persistentVolumeClaim:
81 # claimName: envoy-gateway-wasm-cache
84 # Kubernetes best practice for controllers: use a startupProbe with a generous
85 # failure threshold to avoid premature liveness/readiness failures during initialization.
86 # Ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-startup-probes
122 priorityClassName: null
127 prometheus.io/scrape: 'true'
128 prometheus.io/port: '19001'
130 topologySpreadConstraints: []
133 # Additional volumeMounts on the deployment definition.
134 extraVolumeMounts: []
136 # mountPath: "/etc/foo"
138 # Additional volumes on the deployment definition.
151 # If set to PreferClose, the Envoy fleet will prioritize connecting to the Envoy Gateway pods that are topologically closest to them.
152 trafficDistribution: ""
154 # -- Service type. Can be set to LoadBalancer with specific IP, e.g.:
156 # loadBalancerIP: 10.236.90.20
165 # -- EnvoyGateway configuration. Visit https://gateway.envoyproxy.io/docs/api/extension_types/#envoygateway to view all options.
168 controllerName: gateway.envoyproxy.io/gatewayclass-controller
175createNamespace: false
176# -- Override the namespace for resources deployed by the chart.
177# Defaults to the release namespace.
179kubernetesClusterDomain: cluster.local
180# -- Certgen is used to generate the certificates required by EnvoyGateway. If you want to construct a custom certificate, you can generate a custom certificate through Cert-Manager before installing EnvoyGateway. Certgen will not overwrite the custom certificate. Please do not manually modify `values.yaml` to disable certgen, it may cause EnvoyGateway OIDC,OAuth2,etc. to not work as expected.
199 ttlSecondsAfterFinished: 30
201 allowPrivilegeEscalation: false
206 readOnlyRootFilesystem: true