Tyk Operator

Last updated: 2 minutes read.

What is Tyk Operator?

Tyk Operator is a Kubernetes Operator designed to simplify the management of Tyk API configurations both inside and outside of Kubernetes environments. With our custom resources, Tyk Operator simplifies the processes of deploying and configuring API resources, allowing you to focus more on application development and less on infrastructure management. It is ideal for those who like to manage configurations declaratively or with GitOps workflows via tools such as Argo CD and Flux CD.

Tyk Operator

Why use Tyk Operator?

Managing, checking, and synchronizing APIs from multiple teams across environments can be complex. Tyk Operator provides an efficient way to handle API configurations. Here’s why it matters:

  • Simple custom resource: Tyk’s Classic API Definition is a large and complex JSON document, making maintenance difficult. Operator’s CRD (Custom Resource Definition) is designed to be simple and does not require you to specify default values, resulting in a document that is easy to understand and maintain.
  • Declarative configurations: By using declarative configurations, users can store configurations in Git. Changes can then be managed via Git pull requests, making it easy to compare different API configuration versions. Automatic linting and checking can be implemented, ensuring that changes are properly reviewed and approved before merging.
  • Kubernetes integration: Operator works natively with Kubernetes, allowing both development and operations teams to follow their usual workflows for making changes and automating deployments. You can also benefit from Kubernetes tooling support for manifest management (e.g., using Helm or Kustomize) and GitOps deployment (e.g., using ArgoCD or Flux CD).
  • Automated reconciliation: Once you apply custom resources to your Kubernetes cluster, Operator will regularly check that the actual state at Tyk matches the target state in Kubernetes. This ensures any changes at Tyk, such as unauthorized manual updates or database corruption, can be corrected and the target state reinstated.

Key Features

  1. Manage Classic API definitions
  2. Manage Security policies
  3. Manage Tyk Classic Dev Portal
  4. Kubernetes Ingress Controller

Do You Need Tyk Operator?

Consider using Tyk Operator if:

  • You are running applications in a Kubernetes environment.
  • You need to manage multiple Tyk API Gateway instances efficiently.
  • You want to leverage Kubernetes-native automation for API management.
  • You aim to streamline the operations of your API gateways with minimal manual intervention.

Getting Started

To get started with Tyk Operator, learn about Operator key concepts:

Follow our Installation Guide to set up Tyk Operator in your Kubernetes cluster.