kube-slack icon indicating copy to clipboard operation
kube-slack copied to clipboard

"Container entered status *Running*" in the wrong channel

Open pierluigilenoci opened this issue 6 years ago • 3 comments

Hi, I've installed kube-slack via helm chart.

Basically I configured the slackUrl with an webhook with a default channel for the notifications. I've configured a deployment using kube-slack/slack-channel annotation to push pod notifications to a different "new" channel.

Basically I receive the "Container entered status CrashLoopBackOff" messages in the right "new" channel and the "Container entered status Running" messages in the default one. How is it possible?

I actually run v4.0.0 instead of v3.6.0 to check if this problem is fixed but I get the same behavior in both version.

Thank you in advance.

pierluigilenoci avatar Dec 18 '18 12:12 pierluigilenoci

It's definitely a bug. I'll look into this.

whs avatar Dec 21 '18 01:12 whs

I seems to be unable to reproduce the issue. In our company Slack, both messages appear in the right channel. I found nothing in the code either.

whs avatar Dec 25 '18 08:12 whs

Client: &version.Version{SemVer:"v2.12.3", GitCommit:"eecf22f77df5f65c823aacd2dbd30ae6c65f186e", GitTreeState:"clean"} Server: &version.Version{SemVer:"v2.12.3", GitCommit:"eecf22f77df5f65c823aacd2dbd30ae6c65f186e", GitTreeState:"clean"}

Installed charts NAME REVISION UPDATED STATUS CHART APP VERSION NAMESPACE fluent-bit 6 Wed Jan 30 15:06:16 2019 DEPLOYED fluent-bit-1.5.0 1.0.3 logging kube-slack 6 Wed Jan 16 15:56:42 2019 DEPLOYED kube-slack-0.4.0 v3.6.0 infrastructure

kube version Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.2", GitCommit:"cff46ab41ff0bb44d8584413b598ad8360ec1def", GitTreeState:"clean", BuildDate:"2019-01-13T23:15:13Z", GoVersion:"go1.11.4", Compiler:"gc", Platform:"darwin/amd64"} Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.3", GitCommit:"435f92c719f279a3a67808c80521ea17d5715c66", GitTreeState:"clean", BuildDate:"2018-11-26T12:46:57Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}

Maybe this could help

pierluigilenoci avatar Feb 05 '19 15:02 pierluigilenoci