aboutsummaryrefslogtreecommitdiffstats
path: root/kud/tests/README-composite-vfw.txt
diff options
context:
space:
mode:
Diffstat (limited to 'kud/tests/README-composite-vfw.txt')
-rw-r--r--kud/tests/README-composite-vfw.txt24
1 files changed, 23 insertions, 1 deletions
diff --git a/kud/tests/README-composite-vfw.txt b/kud/tests/README-composite-vfw.txt
index d2018c09..3f334a25 100644
--- a/kud/tests/README-composite-vfw.txt
+++ b/kud/tests/README-composite-vfw.txt
@@ -7,7 +7,29 @@ As written, the vfw-test.sh script assumes 3 clusters
The edge cluster in which vFW will be instantiated should be KUD clusters.
-# Preparations
+# Edge cluster preparation
+
+For status monitoring support, the 'monitor' docker image must be built and
+deployed.
+
+In multicloud-k8s repo:
+ cd multicloud-k8s/src/monitor
+ docker build -f build/Dockerfile . -t monitor
+ <tag and push docker image to dockerhub ...>
+
+Deploy monitor program in each cluster (assumes multicloud-k8s repo is present in cloud)
+ # one time setup per cluster - install the CRD
+ cd multicloud-k8s/src/monitor/deploy/crds
+ kubectl apply -f crds/k8splugin_v1alpha1_resourcebundlestate_crd.yaml
+
+ # one time setup per cluster
+ # update yaml files with correct image
+ # (cleanup first, if monitor was already installed - see monitor-cleanup.sh)
+ cd multicloud-k8s/src/monitor/deploy
+ monitor-deploy.sh
+
+
+# Preparation of the vFW Composit Application
## Prepare the Composite vFW Application Charts and Profiles