diff --git a/05-osm-usage.md b/05-osm-usage.md index b84c91ae072c8871b98290a1f360f8fa75e0b92b..eb696d3db17047a358d5c5ac9eb1ac0822b05215 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 --nsd_name --vim_account --config '{additionalParamsForVnf: [{"member-vnf-index": "", "k8s-namespace": ""}]}' + +# Change the namespace at a KDU level +osm ns-create --ns_name --nsd_name --vim_account --config '{additionalParamsForVnf: [{"member-vnf-index": "", additionalParamsForKdu: [{"kdu_name": "", "k8s-namespace": ""}]}]}' + +# Change the namespace at a global level +osm ns-create --ns_name --nsd_name --vim_account --config '{"k8s-namespace": ""}' +``` + + ## Understanding Day-1 and Day-2 Operations VNF configuration is done in three "days":