You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running botkube on our devops EKS (v1.18.9-eks-d1db3c) cluster which does CI. Jenkins creates things in the devops-jenkins-agents namespace. It does this a lot, and I don't need pod creation/deletion events for that namespace. I've added the namespace to ignore in the v1/pods resources section (that's the only change from the default install using the helm chart) and it still gives me notifications in my Slack channel.
I expect botkube to ignore things for pods in the devops-jenkins-agents namespace
Screenshots
Config looks like it should ignore those events...
But here they are...
Additional context
I swear it worked at one point. I initially installed the chart via terraform, then manually edited the configmap. Pretty sure that worked. I didn't like that because it would break when I deployed again, so I wanted to render the values properly. I switched to this system, which results in a proper looking config file, everything runs, but despite the ignore being there it doesn't ignore.
The text was updated successfully, but these errors were encountered:
Describe the bug
I'm running botkube on our devops EKS (v1.18.9-eks-d1db3c) cluster which does CI. Jenkins creates things in the devops-jenkins-agents namespace. It does this a lot, and I don't need pod creation/deletion events for that namespace. I've added the namespace to ignore in the v1/pods resources section (that's the only change from the default install using the helm chart) and it still gives me notifications in my Slack channel.
To Reproduce
I have botkube installed to an EKS 1.18 cluster using the helm provider with the following config: https://gist.github.com/darkhelmet/9a61ecca6aaf7f4a4dd19ef0cfdccea0
Expected behavior
I expect botkube to ignore things for pods in the devops-jenkins-agents namespace
Screenshots
Config looks like it should ignore those events...
But here they are...
Additional context
I swear it worked at one point. I initially installed the chart via terraform, then manually edited the configmap. Pretty sure that worked. I didn't like that because it would break when I deployed again, so I wanted to render the values properly. I switched to this system, which results in a proper looking config file, everything runs, but despite the ignore being there it doesn't ignore.
The text was updated successfully, but these errors were encountered: