817b8e035e
For now, by default, pod network was taken from OpenShift Machine spec, by looking for "networks" field and get the first item out of it to figure out right subnet. Currently there is another field, where networks can be defined - under "ports" field, where subnet for fixed IPs can be found. Additionally, to avoid confusion, there is another field, which defines primary subnet for the pods - "primarySubnet". Implementation has been adapted to reflect that change: 1. primarySubnet will be examined, to get the subnet id 2. if primarySubnet does not exists, networks field will be examined 3. if there is no networks field (or it doesn't contain subnets), ports field will be examined for subnet id Change-Id: I35b6f2e6288cbe3fd80b74a5da03639d7bd0a765
Team and repository tags
Project description
Kubernetes integration with OpenStack networking
The OpenStack Kuryr project enables native Neutron-based networking in Kubernetes. With Kuryr-Kubernetes it's now possible to choose to run both OpenStack VMs and Kubernetes Pods on the same Neutron network if your workloads require it or to use different segments and, for example, route between them.
- Free software: Apache license
- Documentation: https://docs.openstack.org/kuryr-kubernetes/latest
- Source: https://opendev.org/openstack/kuryr-kubernetes
- Bugs: https://bugs.launchpad.net/kuryr-kubernetes
- Overview and demo: https://superuser.openstack.org/articles/networking-kubernetes-kuryr
- Release notes: https://docs.openstack.org/releasenotes/kuryr-kubernetes/
Contribution guidelines
For the process of new feature addition, refer to the Kuryr Policy.