Kuryr-kubernetes declares, that supported CNI version is 0.3.0, but
it prints to output in format of version 0.2.0.
Kubernetes can't parse it.
This patch modifies CNI output according to 0.3.1, it has a little
difference with version 0.3.0, just in naming of ips field.
Signed-off-by: Alexey Perevalov <email@example.com>
Turns out 99-loopback.conf file isn't really required when running
kuryr-kubernetes. This commit removes its installation from DevStack
plugin and CNI Docker image.
This patch provides an experimental CNI driver. It's primary purpose
is to enable development of other components (e.g. functional tests,
service/LBaaSv2 support). It is expected to be replaced with daemon
to configure VIF and connect it to the pods and a small lightweight
client to serve as CNI driver called by Kubernetes.
NOTE: unit tests are not provided as part of this patch as it is yet
unclear what parts of it will be reused in daemon-based
Partially-Implements: blueprint kuryr-k8s-integration
With this patch, we'll be able to place our cni executables in:
It also allows you to put configuration files for the kuryr cni driver
For now we are not setting any non standard conf. It is foreseeable
though that some configuration like which host device to base the
ipvlan/vlan/macvlan devices off on container-in-vm environments could go
here (Although it could also be in a kuryr.conf for the cni driver).
Signed-off-by: Antoni S. Puimedon <firstname.lastname@example.org>
The config generation was from back when we did not have keystone v3
support, which moved around how it all is generated. This patch puts
kuryr-kubernetes in line with the rest of Kuryr.
Signed-off-by: Antoni Segura Puimedon <email@example.com>
This commit introduces the `kuryr-k8s` service by adding the service
binary and focusing on loading configuration options.
The configuration options are inherited from kuryr-lib project
(http://github.com/openstack/kuryr) and loaded at runtime, together with
the project ones.
These configuration options can be also generated using the
`oslo-config-generator` utility by using:
tox -e genconfig
The service runs as any other OpenStack-based service:
kuryr-k8s [--debug] [--config-file foo] ...
Partial-Implements: blueprint kuryr-k8s-integration
Signed-off-by: Jaume Devesa <firstname.lastname@example.org>
Co-Authored-By: Taku Fukushima <email@example.com>