From d1a12bf27b235ef5ed13bfd92855dfa046783995 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Dulko?= Date: Mon, 20 Jan 2020 16:17:19 +0100 Subject: [PATCH] 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 --- releasenotes/notes/drop-ingress-d78a7a9be8f20da1.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 releasenotes/notes/drop-ingress-d78a7a9be8f20da1.yaml diff --git a/releasenotes/notes/drop-ingress-d78a7a9be8f20da1.yaml b/releasenotes/notes/drop-ingress-d78a7a9be8f20da1.yaml new file mode 100644 index 000000000..7c4bc5f36 --- /dev/null +++ b/releasenotes/notes/drop-ingress-d78a7a9be8f20da1.yaml @@ -0,0 +1,9 @@ +--- +deprecations: + - | + Support for OpenShift's Routes (Ingress) gets removed as is not mantained + nor tested, and openshift route pods can be used instead. + - | + Support for namespace isolation is now deprecated and will be removed on + the first occasion as the same effect can now be achieved using Network + Policies support.