Go to file
Michał Dulko d1a12bf27b Deprecate unmaintaned features
Support for OpenShift Routes (Ingress) is not maintained by anyone, not
really tested and there are better ways to do it, so let's remove that
code from Kuryr.

Support for namespace isolation was done to mimic one of the modes of
openshift-sdn. It doesn't seem to make any sense to keep supporting it
if Network Policy support can provide the same isolation.

Change-Id: I8cfb3c50f491a5dbbfe6fa20b81ee1d0f8c6b4a7
2020-02-01 16:18:02 +00:00
2020-01-10 17:51:52 +01:00
2019-12-13 18:08:14 +08:00
2020-01-10 17:51:52 +01:00
2019-10-14 12:44:47 +00:00
2016-11-18 10:14:56 +03:00
2018-09-25 12:16:08 +02:00
2019-04-19 19:44:54 +00:00
2018-07-16 15:43:10 +00:00
2019-06-17 12:58:37 +02:00
2019-11-19 12:34:54 +01:00
2019-11-13 11:39:10 +01:00
2019-11-19 12:34:54 +01:00
2019-12-20 12:04:13 +01:00
2019-11-19 12:34:54 +01:00
2017-03-15 12:44:19 +00:00
2018-07-16 15:43:10 +00:00
2019-11-19 12:34:54 +01:00

Team and repository tags

image

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.

Contribution guidelines

For the process of new feature addition, refer to the Kuryr Policy.

Description
RETIRED, Kubernetes integration with OpenStack networking
Readme 46 MiB