argocd-notifications
argocd-notifications copied to clipboard
Slack bot - secret "argocd-notifications-secret" not found
Summary
Created notifications to slack and slack-bot
with token
and signingSecret
Notifications works, but slack commands e.g. /argocd list-subscription
which requires signingSecret
from Slack errors with output:
failed to verify request signature: secret "argocd-notifications-secret" not found
Secret is there, we are deploying with official helm chart.
Config map:
apiVersion: v1
data:
context: "argocdUrl: \n"
service.slack: |
token: $slack-token
signingSecret: $slack-signing-secret
Secret
apiVersion: v1
data:
slack-signing-secret: BASE64ENCODEDSECRET
slack-token: BASE64ENCODEDSECRET
kind: Secret
metadata:
annotations:
meta.helm.sh/release-name: argocd
meta.helm.sh/release-namespace: argocd
creationTimestamp: "2022-02-04T11:40:40Z"
labels:
app.kubernetes.io/instance: argocd
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: argocd-notifications
app.kubernetes.io/version: v1.2.1
helm.sh/chart: argocd-notifications-1.8.0
name: argocd-notifications-secret
Tried to give direct secret values inside the configMap
but still no luck. Anyone else experienced this issue?
Diagnostics
What Kubernetes provider are you using? EKS 1.20 What version of Argo CD and Argo CD Notifications are you running? ArgoCD v2.1.7 ArgoCD Notifications v1.2.1
# Paste the logs from the notification controller
Slack-bot gives no log output
# Logs for the entire controller:
kubectl logs -n argocd deployment/argocd-notifications-controller
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
Downgrading to v.1.1.1 solved the issue.
Not running into this in v1.2.1.
What was the output of kubectl -n argocd get pods
and kubectl -n argocd get secrets
?
@leoskyrocker got this issue both on local docker-desktop cluster and in EKS 1.20
Tried to give full cluster-access for bot
service account also.
Pods
argocd-notifications-bot-d7c645967-mfnw9 1/1 Running 0 57m
argocd-notifications-controller-767954cdbf-782c5 1/1 Running 0 56m
Secrets
argocd-notifications-bot-token-pg7ht kubernetes.io/service-account-token 3 126d
argocd-notifications-controller-token-pp57p kubernetes.io/service-account-token 3 126d
argocd-notifications-secret Opaque 2 22h
ConfigMap
argocd-notifications-cm 14 18d
I'm deploying with official Helm chart.
With 1.5.2 it works (uses v1.1.1) With 1.8.0 it does not (uses v1.2.1), but changing only the image for this chart to v1.1.1 fixes it.
This could be a legit issue, I misread earlier, and have not actually tried to use the Slack command myself. Sorry for the confusion @AlbertasG.
Same issue. Does /argocd list-subscriptions
work after downgrading? it doesnt for me
/argocd failed with the error "operation_timeout"
nothing logged
This happens to me too with the helm chart. The default helm chart names the secret and cm as follows:
argocd-notifications-controller-cm
argocd-notifications-controller-secret
You can rename them to what argocd cli is expecting them to be, then it works correctly. Perhaps a flag allowing to set the name of the cm/secret?