Skip to content

Commit b641809

Browse files
committed
feat: init kube monitoring labels adr
1 parent daf781e commit b641809

File tree

1 file changed

+86
-0
lines changed

1 file changed

+86
-0
lines changed
Lines changed: 86 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,86 @@
1+
# 012-greenhouse-kube-monitoring-labels
2+
3+
- Status: [draft] <!-- optional -->
4+
- Deciders: [Richard, Esther, Arno, Akshay, David R.] <!-- optional -->
5+
- Date: [YYYY-MM-DD when the decision was last updated] <!-- optional. To customize the ordering without relying on Git creation dates and filenames -->
6+
- Tags: [greenhouse / cloudoperators] <!-- optional -->
7+
- Technical Story: [description | ticket/issue URL] <!-- optional -->
8+
9+
## Context and Problem Statement
10+
11+
Define which functionalities rely on labels and which labels these are. This should be done for the entire stack (e.g. Metrics, Logs, Alerts, UIs[Supernova, ...] ...)
12+
This also includes indentifying mandatory labels (e.g. owner-info etc.), which are used for alert routing...
13+
14+
The goal of this ADR is to define a common set of labels that can be used across all components of the greenhouse stack. These labels should then also be enforced, defaulted and integrated across Greenhouse.
15+
16+
## Decision Drivers <!-- optional -->
17+
18+
- [driver 1, e.g., a force, facing concern, …]
19+
- [driver 2, e.g., a force, facing concern, …]
20+
-<!-- numbers of drivers can vary -->
21+
22+
## Considered Options
23+
24+
- [option 1]
25+
- [option 2]
26+
- [option 3]
27+
-<!-- numbers of options can vary -->
28+
29+
## Decision Outcome
30+
31+
Chosen option: "[option 1]",
32+
because [justification. e.g., only option, which meets k.o. criterion decision driver | which resolves force force | … | comes out best (see below)].
33+
34+
### Positive Consequences <!-- optional -->
35+
36+
- [e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]
37+
-
38+
39+
### Negative Consequences <!-- optional -->
40+
41+
- [e.g., compromising quality attribute, follow-up decisions required, …]
42+
-
43+
44+
## Pros and Cons of the Options | Evaluation of options <!-- optional -->
45+
46+
### [option 1]
47+
48+
[example | description | pointer to more information | …] <!-- optional -->
49+
50+
| Decision Driver | Rating | Reason |
51+
|---------------------|--------|-------------------------------|
52+
| [decision driver a] | +++ | Good, because [argument a] | |
53+
| [decision driver b] | --- | Good, because [argument b] |
54+
| [decision driver c] | -- | Bad, because [argument c] |
55+
| [decision driver d] | o | Neutral, because [argument d] |
56+
57+
### [option 2]
58+
59+
[example | description | pointer to more information | …] <!-- optional -->
60+
61+
| Decision Driver | Rating | Reason |
62+
|---------------------|--------|-------------------------------|
63+
| [decision driver a] | +++ | Good, because [argument a] | |
64+
| [decision driver b] | --- | Good, because [argument b] |
65+
| [decision driver c] | -- | Bad, because [argument c] |
66+
| [decision driver d] | o | Neutral, because [argument d] |
67+
68+
### [option 3]
69+
70+
[example | description | pointer to more information | …] <!-- optional -->
71+
72+
| Decision Driver | Rating | Reason |
73+
|---------------------|--------|-------------------------------|
74+
| [decision driver a] | +++ | Good, because [argument a] | |
75+
| [decision driver b] | --- | Good, because [argument b] |
76+
| [decision driver c] | -- | Bad, because [argument c] |
77+
| [decision driver d] | o | Neutral, because [argument d] |
78+
79+
## Related Decision Records <!-- optional -->
80+
81+
[previous decision record, e.g., an ADR, which is solved by this one | next decision record, e.g., an ADR, which solves this one | … | pointer to more information]
82+
83+
## Links <!-- optional -->
84+
85+
- [Link type](link to adr) <!-- example: Refined by [xxx](yyyymmdd-xxx.md) -->
86+
-<!-- numbers of links can vary -->

0 commit comments

Comments
 (0)