04c7cb63a4
If a loadBalancerIP is defined on the Service it should be used on the created Load Balancer. However, that is not happening as the LB CRD can be missing the lb_ip field definition, consequently a new Floating IP is allocated to the Load Balancer. This commit fixes the issue by ensuring the lb_ip is present on the CRD if defined on the Service. Closes-Bug: 1893927 Change-Id: Ie626328972587772dbeeaf52f96b312de41026f2 |
||
|---|---|---|
| .zuul.d | ||
| contrib | ||
| devstack | ||
| doc | ||
| etc | ||
| kubernetes_crds | ||
| kuryr_cni | ||
| kuryr_kubernetes | ||
| playbooks | ||
| releasenotes | ||
| tools | ||
| .coveragerc | ||
| .dockerignore | ||
| .gitignore | ||
| .gitreview | ||
| .pre-commit-config.yaml | ||
| .stestr.conf | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| README.rst | ||
| babel.cfg | ||
| cni.Dockerfile | ||
| cni_ds_init | ||
| controller.Dockerfile | ||
| lower-constraints.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
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.