bug: unable to run Lambda DinD setup in k8s with restricted egres #10776
Labels
aws:lambda
AWS Lambda
status: backlog
Triaged but not yet being worked on
type: question
Please ask questions on discuss.localstack.cloud
Is there an existing issue for this?
Current Behavior
We have added restricted egress to our entire infrastructure. When this happened in our CI pipeline, we saw the lambda tests starting to fail. They are unable to reach public.ecr registry to pull that img. I checked the documentation and source code to find a means to use our specific img registry that will proxy to public.ecr, but I came up with no answers.
additional background:
Expected Behavior
I expected a means to set the img that DinD uses to execute the lambda functions where the img is proxied through our img registry proxies (aka, egress allowed).
How are you starting LocalStack?
With a docker-compose file
Steps To Reproduce
run localstack in a k8s environment with restricted egres disallowing the pullling of imgs from
public.ecr.aws/lambda
. Then attempt to run any function. Await failure.Environment
Anything else?
this issue manifests in both our community edition tests as well as our paid pro tests. Regardless it doesn't allow for the injection of the
public.ecr.aws/lambda
img. We'll need to override that to utilize our proxies.The text was updated successfully, but these errors were encountered: