aboutsummaryrefslogtreecommitdiffstats
path: root/deployments/kubernetes/Readme.md
diff options
context:
space:
mode:
authorEric Multanen <eric.w.multanen@intel.com>2020-09-02 14:27:28 -0700
committerEric Multanen <eric.w.multanen@intel.com>2020-09-09 21:42:58 -0700
commit114bbe4e67f875b5dd628bda0b07c2bfed344507 (patch)
treea681f3e57b8262f1e879583fbd7b67d80c211602 /deployments/kubernetes/Readme.md
parent6452065eb2d3b2f0926d16499e0ecedec2382422 (diff)
Create monitor deployment yaml file
Combine all resources into a yaml file for deployment of the monitor program in a cluster. Issue-ID: MULTICLOUD-1065 Signed-off-by: Eric Multanen <eric.w.multanen@intel.com> Change-Id: I4b7029bb62d01dc166ad4e25a89f99d139057e0c
Diffstat (limited to 'deployments/kubernetes/Readme.md')
-rw-r--r--deployments/kubernetes/Readme.md30
1 files changed, 24 insertions, 6 deletions
diff --git a/deployments/kubernetes/Readme.md b/deployments/kubernetes/Readme.md
index b5a99a65..ba319837 100644
--- a/deployments/kubernetes/Readme.md
+++ b/deployments/kubernetes/Readme.md
@@ -1,23 +1,41 @@
-# Steps for running v2 API microservices
+# Steps for running EMCO API microservices
### Steps to install packages
-**1. Create namespace for ONAP4K8s v2 Microservices**
+**1. Create namespace for EMCO Microservices**
`$ kubectl create namespace onap4k8s`
-**2. Create Databases used by ONAP4K8s v2 Microservices for Etcd and Mongo**
+**2. Create Databases used by EMCO Microservices for Etcd and Mongo**
`$ kubectl apply -f onap4k8sdb.yaml -n onap4k8s`
-**3. create ONAP4K8s v2 Microservices**
+**3. create EMCO Microservices**
`$ kubectl apply -f onap4k8s.yaml -n onap4k8s`
### Steps to cleanup packages
-**1. Cleanup ONAP4K8s v2 Microservies**
+**1. Cleanup EMCO Microservies**
`$ kubectl delete -f onap4k8s.yaml -n onap4k8s`
-**2. Cleanup v2 Microservices for Etcd and Mongo**
+**2. Cleanup EMCO Microservices for Etcd and Mongo**
`$ kubectl delete -f onap4k8sdb.yaml -n onap4k8s`
+
+# Steps for running the monitor microservice in clusters
+
+The EMCO microservices utilize the monitor microservice to collect
+status information from clusters to which EMCO deploys applications.
+It must be installed in each cluster to which EMCO deploys applications.
+
+### Steps to install monitor in a cluster
+
+**1. Instantiate the monitor resources
+
+ $ kubectl apply -f monitor-deploy.yaml
+
+### Steps to cleanup monitor in a cluster
+
+**1. Cleanup the monitor resources
+
+ $ kubectl delete -f monitor-deploy.yaml