Chart version: 3.1.2
Api version: v1
App version: 2.0.0
DEPRECATED - Inbucket is an email testing application
Chart Type
Set me up:
helm repo add center
Install Chart:
helm install inbucket center/stable/inbucket
Versions (0)

⚠️ Repo Archive Notice

As of Nov 13, 2020, charts in this repo will no longer be updated. For more information, see the Helm Charts Deprecation and Archive Notice, and Update.


Inbucket is an e-mail testing tool.


This chart is deprecated and no longer supported.


$ helm install stable/inbucket


This chart creates a Inbucket deployment on a Kubernetes cluster using the Helm package manager.


  • Kubernetes 1.8+ with Beta APIs enabled

Installing the Chart

To install the chart with the release name my-release:

$ helm install --name my-release stable/inbucket

The command deploys Inbucket on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.

Uninstalling the Chart

To uninstall/delete the my-release deployment:

$ helm delete my-release

The command removes all the Kubernetes components associated with the chart and deletes the release.


The following table lists the configurable parameters of the Inbucket chart and their default values.

Parameter Description Default
image.repository container image repository jhillyerd/inbucket
image.tag container image tag release-1.2.0
image.pullPolicy container image pull policy IfNotPresent
nodeSelector node labels for pod assignment {}
podAnnotations annotations to be added to pods {}
resources pod resource requests & limits {}
service.annotations annotations for the service {}
service.clusterIP internal cluster service IP ""
service.externalIPs service external IP addresses []
service.loadBalancerIP IP address to assign to load balancer (if supported) ""
service.loadBalancerSourceRanges list of IP CIDRs allowed access to load balancer (if supported) []
service.type type of service to create ClusterIP
service.node.http http port of service. Should be the same you set in INBUCKET_WEB_ADDR ""
service.node.smtp smtp port of service. Should be the same you set in INBUCKET_SMTP_ADDR ""
service.node.pop3 pop3 port of service. Should be the same you set in INBUCKET_POP3_ADDR ""
service.nodePort.http if service.type is NodePort and this is non-empty, sets the http node port of the service ""
service.nodePort.smtp if service.type is NodePort and this is non-empty, sets the smtp node port of the service ""
service.nodePort.pop3 if service.type is NodePort and this is non-empty, sets the pop3 node port of the service ""
ingress.enabled if true, an ingress is created false
ingress.annotations annotations for the ingress {}
ingress.path if true, an ingress is created /
ingress.hosts a list of ingress hosts []
ingress.tls a list of IngressTLS items []
config The inbucket config you can use this configurator to adjust you config. set to defaults

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,

$ helm install --name my-release \
  --set image.tag=release-1.2.0 \

Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,

$ helm install --name my-release -f values.yaml stable/inbucket



This chart was inspired in the Mailhog tool, which is another testing email tool, for more Mailhog.