Project reference ↗

kube-slack brings selected Kubernetes Pod failures into a team's Slack channel. It watches cluster state and sends a message through a webhook, helping operators notice failures without continually inspecting the Kubernetes API. It is useful when those events need a lightweight notification path. A failed Pod is not always a user-facing outage, so the team still needs rules about which notifications matter and how repeated failures should be handled.

Current guidance

The historical stable chart identifies wongnai/kube-slack and marks the chart deprecated. The application watches Kubernetes pod failures and posts notifications through a Slack webhook. Its upstream examples use extensions/v1beta1 for Deployment and rbac.authorization.k8s.io/v1beta1 for ClusterRoleBinding, removed in Kubernetes 1.16 and 1.22 respectively. Current clusters reject those manifests as written; changing the API version also requires checking the replacement API’s required fields.

Decide which pod conditions require a human response. A notification about a failed pod is different from a user-facing availability alert, and repeated short-lived failures can overwhelm a channel. Evaluate deduplication, retry behavior and whether a recovery notification is needed rather than assuming every event deserves an immediate page.

Store the webhook as a secret and scope the watcher’s Kubernetes permissions to the required resources. Review whether pod names, annotations or error details disclose sensitive information to the destination. Test an intentional failure, an unavailable Slack endpoint and controller restart without production impact. The archived chart is a known packaging limitation; this review does not establish that the application itself is retired or that its historical image supports current Kubernetes APIs.

Historical upstream link check · 2026-10-09

The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. GitHub confirms that helm/charts is archived: this is a historical chart distribution, not evidence that the application itself is retired. Link availability does not certify the historical installation instructions or current security support.

Source for this check ↗

Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.

The original record

Historical Kubedex content

Preserved for context. Commands, versions, prices and results below reflect the original research.

kube-slack is a monitoring service for Kubernetes. When a pod has failed, it will publish a message in Slack channel. This chart adds a deployment, listening for cluster-wide pod failures and posting them to your slack channel. A cluster-wide RBAC is created by default, but can also be specified.

Slack is a collaboration hub, where the right people and the right information come together, helping everyone get work done.

Create an incoming webhook:

  • In the Slack interface, click on the gears button (Channel Settings) near the search box.
  • Select “Add an app or integration”
  • Search for “Incoming WebHooks”
  • Click on “Add configuration”
  • Select the channel you want the bot to post to and submit.
  • You can customize the icon and name if you want.

Create a channel for every conversation

In Slack, conversations happen in channels organized by topic, project, team, or whatever makes sense for your company. With channels, the right people don’t get left out and information doesn’t get lost.

Integrate with the services you already use

Slack integrates with the apps and services you and your team already use every day. Information flows into the stream of conversation so everyone can see it or act on it inside Slack.

Collaborate with voice calls, video calls, and screen sharing

Voice calls and video calls built into Slack make it easier to work as effectively online as you do in person, and if you need to show your work, you can share your screen within a video call, too.

Find what you need quickly

Everything in public channels, including messages, files, and integrations, becomes searchable in Slack. Find what you need to get up to speed, catch up on past decisions, and tap into your company’s collective knowledge.

You can use Slack’s free plan as long as you like, with as many people as you like.

Sources & further reading

  1. Historical chart identity
  2. Notifier source and examples
  3. Kubernetes API removals and migration requirements
  4. Recovered historical source (Common Crawl index)

Spotted something that needs another look?

Help improve this page →