aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authoryunlong ying <ying.yunlong@zte.com.cn>2019-04-16 07:38:14 +0000
committerGerrit Code Review <gerrit@onap.org>2019-04-16 07:38:14 +0000
commit46901da51522e44fbac7290e28d72945b5ce47e1 (patch)
tree4641bfabe581ee020ae655b457e3c65e57b5b7be
parentdfe17e42ca2c6236a55f47a40a120a2a143b839d (diff)
parentec7505223056f1ca28708896dba61ed11d6fd724 (diff)
Merge "update vfc doc"
-rw-r--r--docs/platform/installation/installation/vfc-over-oom.rst5
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/platform/installation/installation/vfc-over-oom.rst b/docs/platform/installation/installation/vfc-over-oom.rst
index eac3e477..4d7cc25c 100644
--- a/docs/platform/installation/installation/vfc-over-oom.rst
+++ b/docs/platform/installation/installation/vfc-over-oom.rst
@@ -201,7 +201,7 @@ You will see all the pod is runing
dev-vfc-vfc-zte-vnfm-driver-7dbd4f887-thvvg 2/2 Running 8 79d
-**4 VF-C health check **
+**4 VF-C health check**
========================
When VF-C pod is up, if you want to check the service status, you can visit the following APIs in K8S cluster to check.
@@ -258,6 +258,7 @@ You can visit the http://172.60.2.39:30280/api/vnflcm/v1/swagger.json in the bro
**5 Debug and Testing in running Pod**
======================================
+
When you are doing the testing and would like to replace some new file like binary or some script and want to check the new resut.
Before you replace the file to the running pod,you need to close the pod livenessProbe and readinessProbe first to avoid the pod restart.
@@ -367,9 +368,11 @@ Basic operation of kubernests cluster(Take the namespace of onap in linux client
::
1>Build namespace
+
kubectl create namespace test
2>create pod with 3 replication
+
kubectl run nginx --image=nginx --replicas=3 -n test
3>Pod exposed ports for nginx (target port, source port target-port)