Skip to content
This repository was archived by the owner on May 11, 2022. It is now read-only.

Commit 0615f66

Browse files
committed
quickstarts
1 parent fcf84e5 commit 0615f66

File tree

14 files changed

+74117
-58619
lines changed

14 files changed

+74117
-58619
lines changed

examples/test.didact.yaml

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
metadata:
2+
name: add-healthchecks
3+
spec:
4+
displayName: Adding health checks to your sample application
5+
durationMinutes: 10
6+
icon: ''
7+
description: You just created a sample application. Now, let’s add health checks
8+
to it.
9+
prerequisites: [You completed the "Getting started with a sample" quick start.]
10+
introduction: |-
11+
### This quick start shows you how to add health checks to your sample application.
12+
You should have previously created the **sample-app** application and **nodejs-sample** deployment using the **Get started with a sample** quick start. If you haven't, you may be able to follow these tasks with any existing deployment without configured health checks.
13+
tasks:
14+
- title: Viewing the details of your sample application
15+
description: |-
16+
### To view the details of your sample application:
17+
1. Go to the project your sample application was created in.
18+
2. In the **</> Developer** perspective, go to **Topology**.
19+
3. Click on the **nodejs-sample** deployment to view its details.
20+
21+
A side panel is displayed containing the details of your sample application.
22+
review:
23+
instructions: |-
24+
#### To verify you are viewing the details of your sample application:
25+
Is the side panel titled **nodejs-sample**?
26+
failedTaskHelp: This task isn’t verified yet. Try the task again.
27+
summary:
28+
success: You have viewed the details of your sample app!
29+
failed: Try the steps again.
30+
- title: Verifying that there are no health checks
31+
description: |-
32+
### To verify that there your sample application has no health checks configured:
33+
1. View the information in the **Resources** tab in the side panel.
34+
review:
35+
instructions: |-
36+
#### To verify there are no health checks configured:
37+
Do you see an inline alert stating that **nodejs-sample** does not have health checks?
38+
failedTaskHelp: This task isn’t verified yet. Try the task again.
39+
summary:
40+
success: You have verified that there are no existing health checks!
41+
failed: Try the steps again.
42+
- title: Adding health checks to your sample
43+
description: |-
44+
### To add health checks to your sample:
45+
1. Add health checks to your **nodejs-sample** deployment in one of the following ways: (a) On the side panel, click on the **Actions** menu, where you will see an **Add Health Checks** menu item or (b) Click on the **Add Health Checks** link on the inline notification in the side panel.
46+
2. In the Add Health Checks form, click on the **Add Readiness Probe** link. Leave the default values, and click on the check to add the Readiness Probe.
47+
3. Click on the **Add Liveness Probe** link. Leave the default values, and click on the check to add the Liveness Probe.
48+
4. Click on the **Add Startup Probe** link. Leave the default values, and click on the check to add the Startup Probe.
49+
5. Click **Add** when you’re done.
50+
51+
You will be brought back to the Topology View.
52+
review:
53+
instructions: |-
54+
#### Verify that health checks are now configured:
55+
Is the inline notification gone?
56+
failedTaskHelp:
57+
This task isn’t verified yet. Try the task again, or [read more](https://docs.openshift.com/container-platform/4.6/applications/application-health.html#odc-adding-health-checks)
58+
about this topic.
59+
summary:
60+
success: You have added health checks to your sample app!
61+
failed: Try the steps again.
62+
conclusion: Your sample application now has health checks. To ensure that your application
63+
is running correctly, take the **Monitor your sample application** quick start.
64+
nextQuickStart: [template-id]

0 commit comments

Comments
 (0)