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
{{ message }}
This repository has been archived by the owner on Jan 11, 2021. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: