Skip to content
This repository was archived by the owner on Oct 19, 2024. It is now read-only.

Commit 3281829

Browse files
docs: add troubleshooting errors (#308)
Signed-off-by: Ryota Sakamoto <[email protected]>
1 parent c298b1a commit 3281829

File tree

2 files changed

+44
-0
lines changed

2 files changed

+44
-0
lines changed

docs/troubleshooting-errors.md

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
## Failed to parse new settings
2+
3+
### error converting YAML to JSON
4+
5+
YAML syntax is incorrect.
6+
7+
**incorrect:**
8+
9+
```yaml
10+
apiVersion: v1
11+
kind: ConfigMap
12+
metadata:
13+
name: argocd-notifications-cm
14+
data:
15+
service.slack: |
16+
token: $slack-token
17+
icon: :rocket:
18+
```
19+
20+
**correct:**
21+
22+
```yaml
23+
apiVersion: v1
24+
kind: ConfigMap
25+
metadata:
26+
name: argocd-notifications-cm
27+
data:
28+
service.slack: |
29+
token: $slack-token
30+
icon: ":rocket:"
31+
```
32+
33+
### service type 'xxxx' is not supported
34+
35+
You need to check your argocd-notifications controller version. For instance, the teams integration is to support `v1.1.0` and more.
36+
37+
## Failed to notify recipient
38+
39+
### notification service 'xxxx' is not supported"
40+
41+
You have not defined `xxxx` in `argocd-notifications-cm` or to fail to parse settings.

docs/troubleshooting.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -74,3 +74,6 @@ kubectl exec -it argocd-notifications-controller-<pod-hash> \
7474

7575
{!troubleshooting-commands.md!}
7676

77+
## Errors
78+
79+
{!troubleshooting-errors.md!}

0 commit comments

Comments
 (0)