1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
2 .. http://creativecommons.org/licenses/by/4.0
12 DCAE healthchecks are performed by a separate service.
16 These service is packaged into a Docker image (``onap/org.onap.dcaegen2.deployments.healthcheck-container``),
17 which is built in the ``healthcheck-container`` module in the ``dcaegen2/deployments`` repository.
19 dcae-ms-healthcheck is deployed along with services enabled under (``oom/kubernetes/dcaegen2-services``)
21 This healthcheck container runs as service that exposes a simple Web API. In response to
22 request, the service checks Kubernetes to verify that all of the expected
23 DCAE platform and service components are in a ready state.
25 The service has a fixed list service components identified by json file - `expected-components.json <https://github.com/onap/oom/blob/master/kubernetes/dcaegen2-services/resources/expected-components.json>`_
26 ; these are normally deployed when dcaegen2-services is installed. In addition, the healthcheck service also tracks and checks components that are deployed dynamically after the initial DCAE installation.
28 The healthcheck service is exposed as a Kubernetes ClusterIP Service named
29 `dcae-ms-healthcheck`. The service can be queried for status as shown below.
32 Run the below commands before running "curl dcae-ms-healthcheck"
34 * To get the dcae-ms-healthcheck pod name, run following command:
38 kubectl get pods -n onap | grep dcae-ms-healthcheck
40 * Then enter in to the shell of the container, run the following command (substituting the pod name retrieved by the previous command):
44 kubectl exec -it <dcae-ms-healthcheck pod> -n onap bash
49 $ curl dcae-ms-healthcheck
55 "name": "onap-dcae-hv-ves-collector",
60 "name": "onap-dcae-prh",
65 "name": "onap-dcae-tcagen2",
70 "name": "onap-dcae-ves-collector",
75 "name": "onap-dcae-ves-openapi-manager",