kuryr-kubernetes/kuryr_kubernetes/cni
Michał Dulko 78102c9984 Use virtualenv to build kuryr-cni Docker image
This commit changes the way we produce kuryr-cni Docker image. Previously we've
distributed the kuryr-driver as pyinstaller binary that contained Python 3
interpreter and all the dependencies. This binary was called from CNI. That
approach had some disadvantages, the major being complicated build procedure
and having to see false-positive BrokenPipeError tracebacks in kubelet
logs.

This commit implements distributing kuryr-driver as a virtualenv with
kuryr-kubernetes and all the dependecies installed. That virtualenv is then
copied onto the host system and CNI can easily activate it and run kuryr-cni
binary. This should solve issues caused by pyinstaller.

Closes-Bug: 1747058

Change-Id: I65b01ba27cbe39b66f0a972d12f3abc166934e62
2018-02-02 19:55:44 +01:00
..
binding Fix kubelet retries issues 2018-01-04 19:20:06 +01:00
daemon Use virtualenv to build kuryr-cni Docker image 2018-02-02 19:55:44 +01:00
__init__.py Experimental CNI & VIFBridge binding 2016-12-05 18:05:22 +00:00
api.py CNI split - introducing CNI daemon 2017-11-21 08:50:04 +01:00
handlers.py CNI split - introducing CNI daemon 2017-11-21 08:50:04 +01:00
main.py CNI split - introducing CNI daemon 2017-11-21 08:50:04 +01:00
utils.py CNI split - introducing CNI daemon 2017-11-21 08:50:04 +01:00