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

ocicni is ignoring environment CNI_ARGS and synthesizing a new one #65

Open
space88man opened this issue Nov 1, 2019 · 4 comments
Open

Comments

@space88man
Copy link
Contributor

space88man commented Nov 1, 2019

TL;DR Is there a way to invoke ocicni to "pass-through" CNI_ARGS from the environment instead of synthesizing k8s-type CNI_ARGS?

https://github.com/containers/libpod is a consumer of this package. However, the package is ignoring CNI_ARGS from the environment and synthesizing a k8s friendly(?) version. This prevents podman from influencing CNI plugins like host-local or static.

Presumably because ocicni was only expecting to be used in k8s environment - however standalone users like podman need to be able to pass-through CNI_ARGS to the plugin.

See containers/podman#4398

CNI_ARGS set by user when calling podman:

CNI_ARGS="IP:192.168.125.200;GATEWAY=192.168.125.1 podman ...

CNI_ARGS that the plugin actually sees:

IgnoreUnknown=1;K8S_POD_NAMESPACE=abcd_3;K8S_POD_NAME=abcd_3;K8S_POD_INFRA_CONTAINER_ID=4c7f1903383a9552973ba2deb5ceb2e8b65ab1e06309c8af948b217724718bc3
@vrothberg
Copy link
Member

@space88man are you interested in opening a PR for it?

@rhatdan
Copy link
Contributor

rhatdan commented Feb 18, 2020

Any progress on this issue?

@space88man
Copy link
Contributor Author

space88man commented Feb 19, 2020

@vrothberg - yes - I still am - finally have some time to push this. Sorry for the delay.

@rhatdan
Copy link
Contributor

rhatdan commented Jun 9, 2020

@space88man We are still waiting for this.

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

3 participants