-
Notifications
You must be signed in to change notification settings - Fork 95
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
Consider fetching remote env in a different way #2253
Labels
enhancement
New feature or request
Comments
This is already being done - today, the env is a mix of the proc file and the pod template. The reason behind that is we were too afraid to break it, so we just merged both instead of replacing. Nowaday I know some users have entry points that add/change env and it might be useful, also some env is provided by k8s itself on start (see all the "SERVICE" env names - not in spec but do exist in the container itself). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the agent reads
proc
filesystem to read env of the target. I imagine an alternative solution, where the env would be taken from Pod template and imagePros:
CAP_PTRACE
from the agent.The text was updated successfully, but these errors were encountered: