Is there a way to disable env injection into a pod...
# 🌱|help-and-getting-started
b
I have a module for rabbitmq with an exposed service port. I have another module "app" that i want to deploy that needs an env called RABBITMQ_PORT "app" gets the following rabbitmq envs
Copy code
RABBITMQ_SERVICE_PORT=5672
RABBITMQ_PORT_5672_TCP_ADDR=172.20.84.21
RABBITMQ_SERVICE_HOST=172.20.84.21
RABBITMQ_PORT=tcp://172.20.84.21:5672
RABBITMQ_SERVICE_PORT_HTTP=5672
RABBITMQ_PORT_5672_TCP=tcp://172.20.84.21:5672
RABBITMQ_PORT_5672_TCP_PORT=5672
RABBITMQ_PORT_5672_TCP_PROTO=tcp
the problem is that the app needs RABBITMQ_PORT to be 5672 setting an env: of RABBITMQ_PORT in garden.yml does nothing since it gets overwritten by garden to
tcp://172.20.84.21:5672
is there any way to disable these vars from being injected? garden 0.12 acorn
q
@bland-wolf-59979 Garden isn't re-writing here: from your
env
,
RABBITMQ_PORT=tcp://172.20.84.21:5672
is what's being passed to Garden.
b
i didn't add these envs. the k8s service is adding these 8 envs to the pod. We had to set
RABBITMQ_PORT
to
5672
in the garden.yml in order to override the injected envs. this isn't an issue in garden, we can work around this, thanks!
5 Views