Prerequisites
Helm CLI
See the Helm documentation for instructions about installing helm.Ingress Controller (Optional)
You can skip this step if:
- You already have ingress-nginx installed.
- You don’t need to expose Keep to the internet/network.
Overview
An ingress controller is essential for managing external access to services in your Kubernetes cluster. It acts as a smart router and load balancer, allowing you to expose multiple services through a single entry point while handling SSL termination and routing rules. Keep works best with both ingress-nginx and HAProxy Ingress controllers, but you can customize the helm chart for other ingress controllers too.Nginx Ingress Controller
Check ingress-nginx Installed
You check if you already have ingress-nginx installed:Install ingress-nginx
To read about more installation options, see ingress-nginx installation docs.
HAProxy Ingress Controller
Install ingress-haproxy
To read about more installation options, see haproxy-ingress installation docs.
Installation
With Ingress-NGINX (Recommended)
With Ingress-HAProxy (Recommended)
Without Ingress (Not Recommended)
Accessing Keep
Ingress
If you installed Keep with ingress, you should be able to access Keep.Without Ingress (Port-Forwarding)
Use the following commands to access Keep locally without ingress:Configuring HTTPS
Prerequisites
- Domain Name: Example - keep.yourcompany.com
- TLS Certificate: Private key (tls.key) and certificate (tls.crt)
Create the TLS Secret
Assuming:tls.crtcontains the certificate.tls.keycontains the private key.
Update Helm Values for TLS
values.yaml:

