notifyURL not functional

[fmunteanu]

Update: See the working implementation, which does not require mentioning the username or channel.

I created a Kured app in Slack and tested the functionality with the provided Webhook URL:

curl -X POST -H 'Content-type: application/json' --data '{"text":"Hello, World!"}' https://hooks.slack.com/services/<redacted>/<redacted>/<redacted>

Chart settings:

USER-SUPPLIED VALUES:
configuration:
  concurrency: 1
  endTime: "07:59"
  notifyUrl: https://hooks.slack.com/services/<redacted>/<redacted>/<redacted>
  period: 15m
  rebootDelay: 60s
  startTime: "04:00"
  timeZone: UTC
metrics:
  create: true
  labels:
    release: kube-prometheus-stack
  namespace: kube-system
resources:
  limits:
    cpu: 400m
    memory: 256Mi
  requests:
    cpu: 100m
    memory: 64Mi
service:
  annotations:
    prometheus.io/path: /metrics
    prometheus.io/port: 8080
    prometheus.io/scrape: true
  create: true
  name: kured
tolerations:
- effect: NoSchedule
  key: node-role.kubernetes.io/control-plane
  operator: Exists

I also need some clarifications if the messageTemplate chart settings are related to Slack only.

I was wondering if anyone can shed some light where the issue resides. cc @dholbach @jackfrancis.

[ckotzbauer]

Hey @fmunteanu,
please have a look at our docs: https://kured.dev/docs/configuration/#notifications
We use "shoutrrr" for notifications, you can use any notification-service shoutrrr supports. Nothing is specific to slack here. There's no logic in kured which does a special notification handling, we just submit one of the three message-templates to the given URL via shoutrrr.
There are three different notifications (with three configurable message-templates):

• Draining
• Rebooting
• Uncordoning

Does this answer your question? Any errors on notifying would be printed as warn-log into kured's pod-logs.

[fmunteanu]

Using the documented format fixed the issue:

I noticed there is a mention about the username and channel in kubereboot/kured#482. I created a Slack app assigned to alerts channel and used the generated credentials, there are no issues posting into correct private channel, with correct user. I don't have to mention the username or channel into notifyUrl string:

notifyUrl: slack://<redacted>/<redacted>/<redacted>

[ckotzbauer]

I don't have to mention the username or channel into notifyUrl string

Yes, the separate username argument is deprecated in kured.