5cf4b41772
When the podSelector of a NP is updated, the podSelector on the respective CRD must also be updated with the same value. However, this do not happen in case the field of a label is updated, for example: Label {'app: demo'} is updated to {'context:demo'} the result given is {'app: demo', 'context:demo'} when should be {'context:demo'}. And after that, if the updated label {'context:demo'} is removed from the NP, it will not be removed from the CRD. These cases happen because the podSelector field is a dict and not a list. This commit fixes the issue by changing the merge strategy to JSON Patch, instead of JSON Merge Patch. Change-Id: Ic629c1ba4ac13c2bfaffdf7f904b69abf9521ed3 Closes-Bug: 1810394 |
||
---|---|---|
.zuul.d | ||
contrib | ||
devstack | ||
doc | ||
etc | ||
kubernetes_crds | ||
kuryr_kubernetes | ||
playbooks | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.dockerignore | ||
.gitignore | ||
.gitreview | ||
.pre-commit-config.yaml | ||
.stestr.conf | ||
.testr.conf | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
README.rst | ||
babel.cfg | ||
cni.Dockerfile | ||
cni_ds_init | ||
cni_py3.Dockerfile | ||
controller.Dockerfile | ||
controller_py3.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://git.openstack.org/cgit/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