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
Some users may have private clusters and want to pull any Docker images needed from an internal or private registry instead of the public datawire one. In this case, they'll want an option to pull the ambassador-agent image from their own registry as well.
Feature
Ability to set the registry from where the ambassador-agent image is pulled. In addition to this, it would also be helpful if they could set the name and tag of their image to use. For example, something similar to these values from the traffic manager:
image:
registry: {INTERNAL_REGISTRY}
name: tel2
pullPolicy: IfNotPresent
# Overrides the image tag whose default is the chart appVersion.
tag: ""
The text was updated successfully, but these errors were encountered:
Summary
Some users may have private clusters and want to pull any Docker images needed from an internal or private registry instead of the public
datawire
one. In this case, they'll want an option to pull theambassador-agent
image from their own registry as well.Feature
Ability to set the registry from where the
ambassador-agent
image is pulled. In addition to this, it would also be helpful if they could set the name and tag of their image to use. For example, something similar to these values from the traffic manager:The text was updated successfully, but these errors were encountered: