summaryrefslogtreecommitdiffstats
path: root/docs/sections/design-components
diff options
context:
space:
mode:
Diffstat (limited to 'docs/sections/design-components')
-rw-r--r--docs/sections/design-components/DCAE-MOD/DCAE-MOD-User-Guide.rst5
-rwxr-xr-xdocs/sections/design-components/component-specification/component-type-docker.rst2
-rwxr-xr-xdocs/sections/design-components/component-specification/docker-specification.rst9
3 files changed, 5 insertions, 11 deletions
diff --git a/docs/sections/design-components/DCAE-MOD/DCAE-MOD-User-Guide.rst b/docs/sections/design-components/DCAE-MOD/DCAE-MOD-User-Guide.rst
index 25bf0957..1ea72b33 100644
--- a/docs/sections/design-components/DCAE-MOD/DCAE-MOD-User-Guide.rst
+++ b/docs/sections/design-components/DCAE-MOD/DCAE-MOD-User-Guide.rst
@@ -331,12 +331,9 @@ dashboard at https://<IPAddress>:30418/ccsdk-app/login_external.htm in
our deployment. The name for each component will be appended by the flow
name followed by underscore followed by the component’s name.
-The credentials to access the DCAE Dashboard are-
-
-::
+The credentials to access the DCAE Dashboard
Login: su1234
-
Password: fusion
diff --git a/docs/sections/design-components/component-specification/component-type-docker.rst b/docs/sections/design-components/component-specification/component-type-docker.rst
index a2b0c2a3..cf676c48 100755
--- a/docs/sections/design-components/component-specification/component-type-docker.rst
+++ b/docs/sections/design-components/component-specification/component-type-docker.rst
@@ -30,7 +30,7 @@ to another artifact for a schema. The reference allows for XML and Protocol Buff
but can be used as a pointer to JSON, Delimited Format, and Unstructured
schemas as well.
-.. _metadata:
+.. _component_metadata:
Component Metadata
------------------
diff --git a/docs/sections/design-components/component-specification/docker-specification.rst b/docs/sections/design-components/component-specification/docker-specification.rst
index 63fef9b8..e40af02f 100755
--- a/docs/sections/design-components/component-specification/docker-specification.rst
+++ b/docs/sections/design-components/component-specification/docker-specification.rst
@@ -121,12 +121,9 @@ docker script example
During deployment, the K8S plugin maps the healthcheck defined into
into a Kubernetes readiness probe.
-Kubernetes execs the script in the container (using the `docker exec API
- <https://docs.docker.com/engine/api/v1.29/#tag/Exec>`__ ).
-It will examine the
-script result to identify whether your component is healthy. Your
-component is considered healthy when the script returns ``0`` otherwise
-your component is considered not healthy.
+Kubernetes execs the script in the container (using the `docker exec API <https://docs.docker.com/engine/api/v1.29/#tag/Exec>`__ ).
+It will examine the script result to identify whether your component is healthy. Your
+component is considered healthy when the script returns ``0`` otherwise your component is considered not healthy.
Example: