Skip to content

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

Open
rhatdan opened this issue Jun 13, 2023 Discussed in #18794 · 5 comments
Open

environment variables with Kubernetes Template systemd Integration #18879

rhatdan opened this issue Jun 13, 2023 Discussed in #18794 · 5 comments

Comments

@rhatdan
Copy link
Member

rhatdan commented Jun 13, 2023

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.

@rhatdan rhatdan added the kube label Jun 13, 2023
@jguady
Copy link

jguady commented Jun 13, 2023

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 podman kube play (which in turn would work from the Kubernetes systemd integration) so that I could just worry about setting those there.

@jguady
Copy link

jguady commented Jun 13, 2023

I think #15983 would also provide an acceptable solution to my issue but probably still not ideal for containers.conf.

@rhatdan
Copy link
Member Author

rhatdan commented Jun 13, 2023

@umohnani8 PTAL
Yes the containers.conf needs to be fixed.

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants