-
Notifications
You must be signed in to change notification settings - Fork 712
Allow custom image repository for Envoy Proxy image #6066
Copy link
Copy link
Closed
Description
Description:
We're running a caching AWS ECR for all 3rd party images and would like Envoy Proxy to pull its image from it, without having to pin the image tag/version, and let Envoy Gateway decide on the tag/version.
Currently it's possible to configure the Envoy Proxy image, but only as a single repository + tag combination.
The "KubernetesContainerSpec" has an "image" string parameter, which we set like:
provider:
type: Kubernetes
kubernetes:
envoyDeployment:
container:
image: 1234.dkr.ecr.eu-west-1.amazonaws.com/dockerhub/envoyproxy/envoy:v1.33.1
As you can see, the "image" must include the tag. There is no separate fields for repository and tag.
Being able to specify repository and tag separately, is a common pattern.
It would be great if following Envoy Proxy configuration would be supported:
provider:
type: Kubernetes
kubernetes:
envoyDeployment:
container:
image:
repository: 1234.dkr.ecr.eu-west-1.amazonaws.com/dockerhub/envoyproxy/envoy
tag: v1.33.1
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/apiAPI-related issuesAPI-related issues