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
..
build_cni_daemonset_image	Use virtualenv to build kuryr-cni Docker image	2018-02-02 19:55:44 +01:00
generate_config_file_samples.sh	move config and opt generation to new kuryr-lib	2016-09-26 13:11:47 +00:00
generate_k8s_resource_definitions.sh	Use virtualenv to build kuryr-cni Docker image	2018-02-02 19:55:44 +01:00