Skip to content

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

@dionysius

Description

@dionysius

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions