This is a repository for Tyk helm charts. Please visit the official website to learn about Tyk's Licensing and deployment models and the different Helm Charts availble for Kubernetes deployment.
Helm must be installed to use the charts. Please refer to Helm's documentation to get started.
Once Helm is set up properly, add the repo as follows:
helm repo add tyk-helm https://helm.tyk.io/public/helm/charts/You can then run helm search repo tyk-helm to see the charts.
Helm umbrella chart (chart of charts) is an easy and really flexible way of installing multiple components as a single one. We have following umbrella charts that help you to install group of related tyk components based on your deployment need.
| Umbrella Charts | Description | Status |
|---|---|---|
| tyk-oss | Tyk Open Source | Stable |
| tyk-stack | Tyk Self Managed | Stable |
| tyk-control-plane | Tyk Self Managed (MDCB) Control Plane | Stable |
| tyk-data-plane | Tyk Self Managed (MDCB) Data Plane Tyk Hybrid Data Plane |
Stable |
Tyk Operator's helm chart is managed in tyk-operator repository.
- Redis is required for all of the Tyk installations it must be installed in the cluster or reachable from inside K8s.
- MongoDB or PostgreSQL are only required for the Tyk Self-managed installation and must be installed in the cluster, or reachable from inside K8s. If you are using the MongoDB or SQL pumps in the
tyk-ossinstallation you will require MongoDB or PostgreSQL installed for that as well. - (Coming soon!) There is an easy option for you to spawn a Redis/MongDB/PostgreSQL instance using Bitnami's chart as a sub-chart. This is handy if you want to quickly spin up the whole stack without installing Redis and the Database separately. This is NOT recommended for production use.
For further detail on how to configure Tyk as an Ingress Gateway, or how to manage APIs in Tyk using the Kubernetes API, please refer to our Tyk Operator documentation. The Tyk Operator can be installed along this chart and works with all installation types.