From 5fe1308f4ff1e1154b53a24eb9dd80ed58bd1630 Mon Sep 17 00:00:00 2001 From: Jack Lucas Date: Fri, 7 Feb 2020 15:45:42 -0500 Subject: Remove k8s-bootstrap container k8s-bootstrap container is now in the blueprints repo Issue-ID: DCAEGEN2-2041 Signed-off-by: Jack Lucas Change-Id: I9cc850bf17fa4da985565b623717a2007f785bf1 --- k8s-bootstrap-container/README.md | 19 ------------------- 1 file changed, 19 deletions(-) delete mode 100644 k8s-bootstrap-container/README.md (limited to 'k8s-bootstrap-container/README.md') diff --git a/k8s-bootstrap-container/README.md b/k8s-bootstrap-container/README.md deleted file mode 100644 index 0e8f88d..0000000 --- a/k8s-bootstrap-container/README.md +++ /dev/null @@ -1,19 +0,0 @@ -# DCAE Bootstrap Container -This container is responsible for loading plugins and wagons onto the -DCAE Cloudify Manager instance and for launching DCAE components. - -The Docker image build process loads plugins and blueprints into the -image's file system. At run time, the main script in the container -(`bootstrap.sh`) uploads the plugins to Cloudify Manager, then installs -components using the blueprints. - -The container expects to be started with two environment variables: - - `CMADDR` -- the address of the target Cloudify Manager - - `CMPASS` -- the password for Cloudify Manager - -The container expects input files to use when deploying the blueprints. -It expects to find them in /inputs. The normal method for launching -the container is via a Helm Chart launched by OOM. That chart creates -a Kubernetes ConfigMap containing the input files. The ConfigMap is -mounted as a volume at /inputs. - -- cgit