Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Webhook configured, enabled but not working #620

Closed
eroji opened this issue Jun 16, 2022 · 5 comments
Closed

[BUG] Webhook configured, enabled but not working #620

eroji opened this issue Jun 16, 2022 · 5 comments
Labels
needs-more-info Further information is needed

Comments

@eroji
Copy link

eroji commented Jun 16, 2022

Describe the bug
I installed BotKube on my cluster that's running k8s 1.21.5. I have it configured to send Slack and webhook notifications. However, the webhook portion does not work. The receiving endpoint never got anything from BotKube.

To Reproduce
Steps to reproduce the behavior:

  1. Install BotKube 0.12.4 via deploy-all-in-one.yaml
  2. Change configmap accordingly
  3. Update the secrets configuration
  4. Make a change to a deployment in the monitored namespace

Expected behavior
There should be a webhook call triggered, but nothing was received

Additional context
Here is my config

Showing config for cluster 'dev-cluster'

resources:
- name: apps/v1/deployments
  namespaces:
    include:
    - dev-namespace
  events:
  - create
  - update
  - delete
  - error
  updateSetting:
    fields:
    - spec.template.spec.containers[*].image
    - status.availableReplicas
    includeDiff: true
recommendations: true
communications:
  slack:
    enabled: true
    channel: bot-kubernetes
    notiftype: short
  mattermost:
    enabled: false
    botName: ""
    url: ""
    token: ""
    team: ""
    channel: ""
  discord:
    enabled: false
    token: ""
    botid: ""
    channel: ""
  webhook:
    enabled: true
    url: https://webhook.endpoint/notify
  teams:
    enabled: false
    team: ""
    port: ""
    messagepath: ""
  elasticsearch:
    enabled: false
    username: ""
    server: ""
    skipTLSVerify: false
    awsSigning:
      enabled: false
      awsRegion: ""
      roleArn: ""
    index:
      name: ""
      type: ""
      shards: 0
      replicas: 0
settings:
  clustername: dev-cluster
  kubectl:
    enabled: false
    commands:
      verbs: []
      resources: []
    defaultNamespace: ""
    restrictAccess: false
  configwatcher: true
  upgradeNotifier: true
@eroji eroji added the bug Something isn't working label Jun 16, 2022
@pkosiec
Copy link
Member

pkosiec commented Jun 17, 2022

Hi @eroji, could you please see the logs from the BotKube container?
A few days ago I tested webhook configuration and it worked fine, however I used the latest image from develop.

To confirm you encounter an issue on BotKube side, you can try to follow the guide https://www.botkube.io/contribute/webhook-develop/ and configure BotKube with sample web server which handles incoming requests.

@pkosiec pkosiec added needs-more-info Further information is needed and removed bug Something isn't working labels Jun 17, 2022
@eroji
Copy link
Author

eroji commented Jun 17, 2022

I just looked at the botkube pod, but it's overwhelmed with Slack unmarshalling errors since I have Slack configured. The deployment changes does create Slack notifications however, but not webhook calls.

I will try the echo-server you suggested.

@pkosiec
Copy link
Member

pkosiec commented Jun 17, 2022

Right, the issue with Slack unmarshall errors when using Huddles is resolved in #579 and will be followed-up with #619. If the echo-server will work for you, please try to look for errors specific for the outgoing webhook integration.

Thank you!

@pkosiec
Copy link
Member

pkosiec commented Jul 21, 2022

Hey @eroji, any news regarding your issue? Have you been able to test webhook integration with the echo server?

@pkosiec
Copy link
Member

pkosiec commented Aug 25, 2022

Closing because of inactivity. I couldn't reproduce the issue. Feel free to reopen it if you have more questions 🙂

@pkosiec pkosiec closed this as completed Aug 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-more-info Further information is needed
Projects
None yet
Development

No branches or pull requests

2 participants