From eaec1de8f74205c57a1ce417e5ad03ca35fb35dd Mon Sep 17 00:00:00 2001 From: lagaceg Date: Mon, 30 Dec 2019 14:39:08 +0100 Subject: [PATCH] typo in "Management of K8s clusters" section, option "--k8s_nets" that shall have been "--k8s-nets" --- 06-osm-platform-configuration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/06-osm-platform-configuration.md b/06-osm-platform-configuration.md index 2c743c2..15dd8f3 100644 --- a/06-osm-platform-configuration.md +++ b/06-osm-platform-configuration.md @@ -290,7 +290,7 @@ As previously discussed, OSM supports the deployment of CNFs/KNFs over existing Hence, in other to support this case, OSM's NBI provides a mechanism to be informed about existing K8s clusters. The corresponding CLI client command is the following: ```bash -osm k8scluster-add --creds --vim --version [--namespace "namespace_name"] [--cni "cni_plugin"] --k8s_nets '{(k8s_net1:vim_network1) [,(k8s_net2:vim_network2) ...]}' +osm k8scluster-add --creds --vim --version [--namespace "namespace_name"] [--cni "cni_plugin"] --k8s-nets '{(k8s_net1:vim_network1) [,(k8s_net2:vim_network2) ...]}' ``` Where: @@ -307,7 +307,7 @@ Where: - `namespace`. By default, it will use `kube-system` for this operation. - `VIM_target`: The VIM where the cluster would reside or be attached (the case of bare metal clusters is simply considered a particular case here). - `ver`: K8s version -- `k8s_nets`: list of VIM networks where the cluster is accessible via L3 routing, in (key,value) format, where: +- `k8s-nets`: list of VIM networks where the cluster is accessible via L3 routing, in (key,value) format, where: - The _key_ will be used to refer to a given cluster's network (e.g. "mgmt", "external", etc.) - The _value_ will be used to refer to a VIM network that provides L3 access to that cluster network. - Optionally: -- GitLab