From df9c581007e56fc752fe65091f085e2a946a46e0 Mon Sep 17 00:00:00 2001 From: Harry Zhang Date: Wed, 27 Sep 2017 15:35:32 +0800 Subject: [PATCH] Clarify work with kuryr-kubernetes Change-Id: Ia679f1b5f674d09b720a8ab39809bb16fa0dd8a3 --- doc/source/stackube_scope_clarification.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/stackube_scope_clarification.rst b/doc/source/stackube_scope_clarification.rst index 7f13477..85f3b49 100644 --- a/doc/source/stackube_scope_clarification.rst +++ b/doc/source/stackube_scope_clarification.rst @@ -56,7 +56,7 @@ What’s the difference between other plugin projects? #. Kuryr - * This is a Neutron network plugin for Docker network model, which is not directly supported in Kubernetes. Kuryr can provide CNI interface, but Stackube also requires tenant aware network management which is not included in Kuryr. + * This is a Neutron network plugin for Docker network model, which is not directly supported in Kubernetes. Kuryr can provide CNI interface, but Stackube also requires tenant aware network management which is not included in Kuryr. We will evaluate and propose our multi-tenant model to kuryr-kubernetes as a long term effort, then we can move to use kuryr-kubernetes as the default network plugin. #. Fuxi