From dab0be7327dffdbfe220c96e265706dc919f6374 Mon Sep 17 00:00:00 2001 From: Jack Lucas Date: Thu, 23 May 2019 18:21:17 -0400 Subject: Pull DCAE plugins from Nexus Change-Id: Ifca0978cca90e00f0ad59702b2024d0970df8ec9 Issue-ID: DCAEGEN2-1520 Signed-off-by: Jack Lucas --- k8s-bootstrap-container/README.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) (limited to 'k8s-bootstrap-container/README.md') diff --git a/k8s-bootstrap-container/README.md b/k8s-bootstrap-container/README.md index 614669b..0e8f88d 100644 --- a/k8s-bootstrap-container/README.md +++ b/k8s-bootstrap-container/README.md @@ -2,9 +2,8 @@ This container is responsible for loading plugins and wagons onto the DCAE Cloudify Manager instance and for launching DCAE components. -The script builds plugins and loads blueprints for the DCAE components -to be deployed into the container image -at image build time. At run time, the main script in the container +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. @@ -15,6 +14,6 @@ The container expects to be started with two environment variables: 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 +a Kubernetes ConfigMap containing the input files. The ConfigMap is mounted as a volume at /inputs. -- cgit 1.2.3-korg