-
Notifications
You must be signed in to change notification settings - Fork 2.6k
environment variables with Kubernetes Template systemd Integration #18879
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi Rhatdan! Thank you for opening this. I was just about to do this as well. Let me know what all information I can help provide. The ideal situation for me, would be to have the environment variables (http_proxy, https_proxy) picked up on |
I think #15983 would also provide an acceptable solution to my issue but probably still not ideal for containers.conf. |
@umohnani8 PTAL |
A friendly reminder that this issue had no activity for 30 days. |
A friendly reminder that this issue had no activity for 30 days. |
Discussed in #18794
Originally posted by jguady June 5, 2023
Long title, hopefully somewhat self explanatory.
So I'm trying to use podman to deploy our services/pod. I'm also trying to take advantage of the [email protected] systemd template to manage my pod.
However I'm also trying to set the http_proxy and https_proxy variables in the containers environment. For some reason the variables are not getting passed into the containers even if they are set in the host environment.
Is there a recommendation for how to do this? I am fairly new to kubernetes but it sounds like I might need to create configmap? Ideally I could just pass it in with my .yml file. like ${http_proxy} but it seems to pick that value up literally.
The text was updated successfully, but these errors were encountered: