Skip to content

Commit

Permalink
Clarify SLO AlertPolicy
Browse files Browse the repository at this point in the history
  • Loading branch information
kenfinnigan committed Jun 22, 2022
1 parent 9bd7d90 commit 9780de8
Showing 1 changed file with 5 additions and 3 deletions.
8 changes: 5 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -210,7 +210,7 @@ spec:
isRolling: false # if omitted assumed `false` if `calendar:` is present
budgetingMethod: Occurrences | Timeslices
objectives: # see objectives below for details
alertPolicies: # see alert policies below details
alertPolicies: # see alert policies below for details
```

##### Notes (SLO)
Expand All @@ -237,8 +237,10 @@ spec:
section. If `thresholdMetric` has been defined, only one Threshold can be defined.
However if using `ratioMetric` then any number of Thresholds can be defined.

- **alertPolicies\[ \]** *AlertPolicy*, optional field, described in [Alert Policies](#alertpolicy)
section.
- **alertPolicies\[ \]** *AlertPolicy*, optional field.
section. An alert policy can be defined inline or can refer to an [Alert Policies](#alertpolicy) object,
in which case the following are required:
- **alertPolicyRef** *string*: this is the name or path to the AlertPolicy

##### Objectives

Expand Down

0 comments on commit 9780de8

Please sign in to comment.