charts/charts/stable/protonmail-bridge

protonmail-bridge

Container for protonmail bridge to work on the network.

This chart is not maintained by the upstream project and any issues with the chart should be raised here

Source Code

• https://github.com/shenxn/protonmail-bridge-docker
• https://hub.docker.com/r/shenxn/protonmail-bridge

Requirements

Kubernetes: >=1.16.0-0

Dependencies

Repository	Name	Version
https://library-charts.k8s-at-home.com	common	2.3.1

TL;DR

helm repo add k8s-at-home https://k8s-at-home.com/charts/
helm repo update
helm install protonmail-bridge k8s-at-home/protonmail-bridge

Installing the Chart

To install the chart with the release name protonmail-bridge

helm install protonmail-bridge k8s-at-home/protonmail-bridge

Uninstalling the Chart

To uninstall the protonmail-bridge deployment

helm uninstall protonmail-bridge

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

Configuration

Read through the values.yaml file. It has several commented out suggested values. Other values may be used from the values.yaml from the common library.

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

helm install protonmail-bridge \
  --set env.TZ="America/New York" \
    k8s-at-home/protonmail-bridge

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

helm install protonmail-bridge k8s-at-home/protonmail-bridge -f values.yaml

Custom configuration

Once installed do the following to configure the application within the pod:

1. Get the name of your deployed pod kubectl get pods
2. Run interactively on the pod (setup only) kubectl exec --stdin --tty protonmail-bridge-deployment-6c79fd7f84-ftwcw -- /bin/bash
3. Once logged in, execute the init command bash /protonmail/entrypoint.sh init
4. You should now see the CLI for protonmail-bridge, authenticate with login
5. (optional) If you use split address mode, change mode and info are good for printing the details.
6. Copy your SMTP server info (or IMAP, your choice)
7. Delete the active pod so a new one gets created (which will properly fire up with your persisted settings)

Values

Important: When deploying an application Helm chart you can add more values from our common library chart here

Key	Type	Default	Description
env	object	{}
image.pullPolicy	string	"IfNotPresent"
image.repository	string	"shenxn/protonmail-bridge"
image.tag	string	"1.5.7-1"
ingress.enabled	bool	false
persistence.config.enabled	bool	true
persistence.config.mountPath	string	"/root"
service.port.name	string	"smtp-service"
service.port.port	int	25
strategy.type	string	"Recreate"

Changelog

All notable changes to this application Helm chart will be documented in this file but does not include changes from our common library. To read those click here.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

3.3.2

Added

• Added icon url.

Changed

• N/A

Removed

• N/A

1.0.0

Added

• N/A

Changed

• N/A

Removed

• N/A

Support

• See the Docs
• Open an issue
• Ask a question
• Join our Discord community

---

Autogenerated from chart metadata using helm-docs v1.5.0