+::
+
+ ubuntu@oom-mr01-rancher:~$ kubectl -n onap get svc|grep vnflcm
+ vfc-vnflcm ClusterIP 10.43.71.4 <none> 8801/TCP 87d
+ ubuntu@oom-mr01-rancher:~$ curl http://10.43.71.4:8801/api/vnflcm/v1/swagger.json
+ {"swagger": "2.0", "info": {"title": "vnflcm API", "description": "\n\nThe `swagger-ui` view can be found [here](/api/vnflcm/v1/swagger).\n
+ The `ReDoc` view can be found [here](/api/vnflcm/v1/redoc).\nThe swagger YAML document can be found [here](/api/vnflcm/v1/swagger.yaml).\n
+ The swagger JSON document can be found [here](/api/vnflcm/v1/swagger.json)."........
+
+
+Because VF-C expose service by ClusterIP, so that you can only visit the APIs in K8S cluster.
+If you want to visit VF-C APIs outside of K8S cluster, you can visit these APIs via MSB, because all VF-C APIs have been registered to MSB.
+You can execute the following steps:
+
+::
+
+ ubuntu@oom-mr01-rancher:~$ kubectl -n onap get pod -o wide|grep msb-iag
+ dev-msb-msb-iag-6fbb5b4dbd-pxs8z 2/2 Running 4 28d 10.42.72.222 mr01-node1 <none>
+ ubuntu@oom-mr01-rancher:~$ cat /etc/hosts |grep mr01-node1
+ 172.60.2.39 mr01-node1
+ ubuntu@oom-mr01-rancher:~$ kubectl -n onap get svc|grep msb-iag
+ msb-iag NodePort 10.43.213.250 <none> 80:30280/TCP,443:30283/TCP 87d
+ ubuntu@oom-mr01-rancher:~$ curl http://172.60.2.39:30280/api/vnflcm/v1/swagger.json
+ {"swagger": "2.0", "info": {"title": "vnflcm API", "description": "\n\nThe `swagger-ui` view can be found [here](/api/vnflcm/v1/swagger).\n
+ The `ReDoc` view can be found [here](/api/vnflcm/v1/redoc).\nThe swagger YAML document can be found [here](/api/vnflcm/v1/swagger.yaml).\n
+ The swagger JSON document can be found [here](/api/vnflcm/v1/swagger.json)."........
+
+
+You can visit the http://172.60.2.39:30280/api/vnflcm/v1/swagger.json in the browser
+
+
+**4 Debug and Testing in running Pod**