How to install Flagsmith on Kubernetes with use of Helm
This guide will walk you through the process of installing Flagsmith using Helm, the Kubernetes package manager, ensuring a smooth and efficient setup.
Before we begin, ensure you have the following tools installed and configured:
First, add the repository containing the Flagsmith helm chart:
helm repo add flagsmith https://flagsmith.github.io/flagsmith-charts
helm repo update
helm search repo flagsmith
Isolating applications within Kubernetes namespaces is a good practice. To deploy Flagsmith in its own namespace:
kubectl create namespace flagsmith
Now, you'll install Flagsmith. The helm chart name is "flagsmith":
helm install flagsmith flagsmith/flagsmith --namespace flagsmith --create-namespace
After installation, verify that your Flagsmith deployment is running smoothly:
kubectl get pods --namespace flagsmith
kubectl get all --namespace flagsmith
This process may require customizing your deployment through a customized values.yaml file, which specifies configuration options.
helm install flagsmith flagsmith/flagsmith --values values.yaml --namespace flagsmith
Accessing Flagsmith will depend on your chosen service configuration (LoadBalancer, NodePort, or Ingress). For Ingress access, ensure an Ingress controller is operational in your cluster.
Follow the instructions in the helm install notes, the output of Step 3.
Fully managed and 14 day free trial and 100% money back guarantee
| Extra 1 CPU & 2GB memory | 25 EUR per month |
| Extra 100GB storage (files, database, logs and backups) | 25 EUR per month |
| Private networking, your own IP address or tunnels | 25 EUR per month |
| Premium SLA: 99.95% uptime, 4-hour P1 response, 14 days of backups | 99 EUR per month |
| Enterprise SLA: 99.99% uptime (multiple replicas), 2-hour P1 response 24/7, 30 days of backups | 499 EUR per month |
Annual Get 2 months for free, 17% discount on a yearly plan!
Monthly plans can be cancelled at any time, no commitment.