@@ -53,21 +53,20 @@ core services.
53
53
The script starts by running sanity checks to verify that it is executed from
54
54
the ` root ` account.
55
55
56
- Then, executes ` microshift healthcheck ` command with following options:
56
+ Then, it executes ` microshift healthcheck ` command with following options:
57
57
- ` -v=2 ` to increase verbosity of the output
58
58
- ` --timeout="${WAIT_TIMEOUT_SECS}s" ` to override default 300s timeout value
59
59
- ` --namespace busybox ` to specify the Namespace of the workloads
60
60
- ` --deployments busybox-deployment ` to specify Deployment to check the readiness of
61
61
62
- Internally, ` microshift healthcheck ` with above set of parameters, for a
63
- specified time, checks if workload of provided type exists, then verifies its
64
- status so the amount of ready replicas (Pods) matches the expected amount.
62
+ Internally, ` microshift healthcheck ` checks if workload of the provided type exists and verifies its
63
+ status for the specified timeout duration, so the amount of ready replicas (Pods) matches the expected amount.
65
64
66
65
` microshift healthcheck ` also accepts other parameters to specify other kinds
67
66
of workload: ` --daemonsets ` and ` --statefulsets ` . These options take
68
67
comma-delimited list of resources, e.g.: ` --daemonsets ovnkube-master,ovnkube-node ` .
69
68
70
- Alternatively, an ` --custom ` option can be used with a JSON string, for example:
69
+ Alternatively, a ` --custom ` option can be used with a JSON string, for example:
71
70
```
72
71
microshift healthcheck --custom '{"openshift-storage":{"deployments": ["lvms-operator"], "daemonsets": ["vg-manager"]}, "openshift-ovn-kubernetes":{"daemonsets": ["ovnkube-master", "ovnkube-node"]}}'
73
72
```
0 commit comments