@@ -1190,7 +1190,7 @@ The options used to add the cluster are the following:
-`--description`: Give a description to your Kubernetes cluster
-`--k8s-nets`: It is a dictionary of the cluster network, where the `key` is an arbitrary name and the `value` of the dictionary is the name of the network in the VIM. In case your k8s cluster is not located in a VIM, you could use '{net1: null}'
## Adding repositories to OSM
### Adding repositories to OSM
You might need to add some repos from where to download helm charts required by the KNF:
@@ -1202,11 +1202,11 @@ osm repo-list
osm repo-show bitnami
```
## KNF Service on-boarding
### KNF Service on-boarding
KNFs can be on-boarded using Helm Charts or Juju Bundles. In the following section is shown an example with Helm Chart and for Juju Bundles.
### KNF Helm Chart
#### KNF Helm Chart
Once the cluster is attached to your OSM, you can work with KNF in the same way as you do with any VNF. You can onboard them. For instance, you can use the example below of a KNF consisting of a single Kubernetes deployment unit based on OpenLDAP helm chart.
@@ -1292,9 +1292,9 @@ osm repo-delete elastic
osm k8scluster-delete cluster
```
## KNF juju-bundle
#### KNF Juju Bundle
This is an example on how to onboard a service that use a juju-bundle. For this example the service to be onboarded is a mediawiki that is comprised by a mariadb-k8s database and a mediawiki-k8s frontend.
This is an example on how to onboard a service that uses a Juju Bundle. For this example the service to be onboarded is a mediawiki that is comprised by a mariadb-k8s database and a mediawiki-k8s frontend.