This is a WIP repository for new Tyk helm charts. We will roll out new component charts and umbrella charts here as they are ready. Please visit the respective pages for each chart to learn how to install the chart and find out all the information relevant to that chart.

Note Breaking changes may be introduced before stable release.

• tyk-gateway
• tyk-pump
• tyk-dashboard (Coming soon!)
• tyk-mdcb (Coming soon!)
• tyk-portal (Coming soon!)
• tyk-tib (Coming soon!)
• tyk-operator (Coming soon!)

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.

• tyk-oss
• tyk-mdcb-data-plane
• tyk-self-managed-single-dc (Coming Soon!)
• tyk-mdcb-control-plane (Coming soon!)

• 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-oss installation 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.