Skip to content
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

Are you sure you want to pass every env on plugin invocation? #1102

Open
dionysius opened this issue Jun 27, 2024 · 1 comment
Open

Are you sure you want to pass every env on plugin invocation? #1102

dionysius opened this issue Jun 27, 2024 · 1 comment

Comments

@dionysius
Copy link

env := os.Environ()

While debugging an issue I had with our custom CNI plugin I just found out that libcni forwards every env variable of the program calling CNI.

While I could manage the programs env this leads me to the question whether this feature is really a good idea. Shouldn't libcni invoke plugins only with known CNI env variables?

In my case it was an env LOG_TARGET=stdout which made our custom CNI plugin to output debugging info to stdout and thus break the json output.

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

No branches or pull requests

2 participants
@dionysius and others