From eaa5b6ccf769f60c2785b659d4738cc4d417cf44 Mon Sep 17 00:00:00 2001
From: vegall <lvega@whitestack.com>
Date: Thu, 4 Jul 2024 20:45:30 +0000
Subject: [PATCH 1/2] Adds missing documentation

---
 05-osm-usage.md | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/05-osm-usage.md b/05-osm-usage.md
index b84c91a..6e98b82 100644
--- a/05-osm-usage.md
+++ b/05-osm-usage.md
@@ -470,6 +470,7 @@ You can try it using one of the examples of the hackfest (**packages: [hackfest_
 
 ```bash
 osm ns-create --ns_name hf-basic --nsd_name hackfest_basic-ns
+```
 
 With the previous hackfest example, according to [VNF data model](https://osm-download.etsi.org/repository/osm/debian/ReleaseFIFTEEN/docs/osm-im/osm_im_trees/etsi-nfv-vnfd.html) you will add in VNF Descriptor:
 
@@ -790,6 +791,22 @@ An existing flavor can be used by passing it's ID to `vim-flavor-id` at the VDU
 ```
 
 
+#### Instantiating a NS-KNF in a custom namespace
+
+To deploy a KNF in a Kubernetes custom namespace, you have three ways to do it:
+
+```bash
+# Change the namespace at a VNFD level
+osm ns-create --ns_name <ns-instance-name> --nsd_name <cnf-name> --vim_account <vim-target-name> --config '{additionalParamsForVnf: [{"member-vnf-index": "<vnf-index>", "k8s-namespace": "<namespace>"}]}'
+
+# Change the namespace at a KDU level
+osm ns-create --ns_name <ns-instance-name> --nsd_name <cnf-name> --vim_account <vim-target-name> --config '{additionalParamsForVnf: [{"member-vnf-index": "<vnf-index>", additionalParamsForKdu: [{"kdu_name": "<kdu_name>", "k8s-namespace": "<namespace>"}]}]}'
+
+# Change the namespace at a global level
+osm ns-create --ns_name <ns-instance-name> --nsd_name <cnf-name> --vim_account <vim-target-name> --config '{"k8s-namespace": "<namespace>"}'
+```
+
+
 ## Understanding Day-1 and Day-2 Operations
 
 VNF configuration is done in three "days":
-- 
GitLab


From 0d522566598fa7ae82cbf94d491ea97af269948d Mon Sep 17 00:00:00 2001
From: vegall <lvega@whitestack.com>
Date: Thu, 4 Jul 2024 20:49:12 +0000
Subject: [PATCH 2/2] Fix names in the command

Signed-off-by: vegall <lvega@whitestack.com>
---
 05-osm-usage.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/05-osm-usage.md b/05-osm-usage.md
index 6e98b82..eb696d3 100644
--- a/05-osm-usage.md
+++ b/05-osm-usage.md
@@ -797,13 +797,13 @@ To deploy a KNF in a Kubernetes custom namespace, you have three ways to do it:
 
 ```bash
 # Change the namespace at a VNFD level
-osm ns-create --ns_name <ns-instance-name> --nsd_name <cnf-name> --vim_account <vim-target-name> --config '{additionalParamsForVnf: [{"member-vnf-index": "<vnf-index>", "k8s-namespace": "<namespace>"}]}'
+osm ns-create --ns_name <ns-instance-name> --nsd_name <nsd-name> --vim_account <vim-target-name> --config '{additionalParamsForVnf: [{"member-vnf-index": "<vnf-index>", "k8s-namespace": "<namespace>"}]}'
 
 # Change the namespace at a KDU level
-osm ns-create --ns_name <ns-instance-name> --nsd_name <cnf-name> --vim_account <vim-target-name> --config '{additionalParamsForVnf: [{"member-vnf-index": "<vnf-index>", additionalParamsForKdu: [{"kdu_name": "<kdu_name>", "k8s-namespace": "<namespace>"}]}]}'
+osm ns-create --ns_name <ns-instance-name> --nsd_name <nsd-name> --vim_account <vim-target-name> --config '{additionalParamsForVnf: [{"member-vnf-index": "<vnf-index>", additionalParamsForKdu: [{"kdu_name": "<kdu-name>", "k8s-namespace": "<namespace>"}]}]}'
 
 # Change the namespace at a global level
-osm ns-create --ns_name <ns-instance-name> --nsd_name <cnf-name> --vim_account <vim-target-name> --config '{"k8s-namespace": "<namespace>"}'
+osm ns-create --ns_name <ns-instance-name> --nsd_name <nsd-name> --vim_account <vim-target-name> --config '{"k8s-namespace": "<namespace>"}'
 ```
 
 
-- 
GitLab