Tyk Operator Release Notes - Tyk Documentation

Licensed Protected Product This page contains all release notes for Tyk Operator displayed in reverse chronological order

Support Lifetime

Only the most recent Tyk Operator release is supported. We recommend staying current to minimise exposure to security vulnerabilities from third party dependencies.

1.5 Release Notes

1.5.0 Release Notes

Release Date 23 September 2026

Release Highlights

This release delivers a major expansion of GitOps coverage for Tyk Dashboard resources, along with a first release of API Governance support and several reliability improvements. Full declarative management of Tyk Dashboard resources Tyk Operator now manages several new Kubernetes Custom Resources, closing key gaps that previously prevented full programmatic control of Tyk Dashboard configuration and required manual Dashboard configuration or ad hoc Kubernetes Jobs calling the Admin API:

TykSession: Client access control and tracking Session.
TykCertificate: TLS certificate, with automatic reconciliation when the underlying Kubernetes Secret is rotated by tools like cert-manager or Vault.
TykIdentityProfile: Tyk Identity Broker (TIB) profile for Dashboard Single Sign-On.
TykOAuthClient: OAuth 2.0 client used with Tyk OAuth 2.0 authentication method.
TykWebhook: Webhook handler for Gateway events.
TykUserGroup: Dashboard user groups
While user groups can now be defined declaratively, individual Dashboard user accounts are not managed via CRDs and continue to be configured through the Dashboard API or UI.

API Governance This release introduces support for Tyk’s API Governance capability: a new TykRuleset CRD lets you declare Spectral-based governance rulesets as Kubernetes resources (inline or referencing a ConfigMap/Secret), and Tyk OAS API definitions applied through the Operator can now be evaluated against active rulesets, including an admission webhook that can deny a non-compliant kubectl apply outright. For a comprehensive list of changes, please refer to the detailed changelog below.

Breaking Changes

This release has no breaking changes.

Dependencies

3rd Party Dependencies & Tools

Third Party Dependency	Tested Versions	Compatible Versions	Comments
Kubernetes	1.30.x to 1.36.x	1.28.x to 1.36.x

Given the time difference between your upgrade and the release of this version, we recommend customers verify the ongoing support of third-party dependencies they install, as their status may have changed since the release.

Deprecations

There are no deprecations in this release.

Upgrade instructions

Go to the Upgrading Tyk Operator section for detailed upgrade instructions.

Downloads

Docker image v1.5.0
- docker pull tykio/tyk-operator:v1.5.0
Helm chart
- tyk-charts v5.4.0

Changelog

Changed

Updated to Go 1.26

Tyk Operator has been updated to Go 1.26.

Added

Added TykRuleset CRD for declarative Governance ruleset management

A new TykRuleset custom resource lets you declare Tyk’s API Governance rulesets, Spectral-based rules that lint your Tyk OAS APIs for compliance, as Kubernetes resources, instead of managing them only through the Dashboard. The ruleset’s category list, action (none/warn/block), active state, and Spectral rule body can all be version-controlled and rolled back through Git. The Spectral rule body can be supplied inline in the resource, or via a reference to a ConfigMap or Secret, letting large or sensitive rulesets live outside the CR. The Operator keeps the ruleset in sync with the Dashboard as the resource or its referenced object changes.For more information, visit Governance via Operator

Added admission webhook and reconcile-time Governance evaluation for Tyk OAS APIs

Tyk OAS API definitions applied through the Operator can now be evaluated against active Governance rulesets (see TykRuleset above). A Kubernetes admission webhook can deny a kubectl apply outright when a matching ruleset with the block action has error-level findings, showing up to five violations inline; a ruleset with the warn action instead admits the object with an inline warning. Separately, the reconciler evaluates the same rulesets and records the outcome on status.governancePreflight and as a Kubernetes Event, purely for visibility; it never blocks or withholds the Dashboard sync based on a governance result.Evaluation is opt-in: it only runs when an API’s categories intersect an active TykRuleset’s categories, and results are cached against a hash of the OpenAPI document plus the matched ruleset set, so unrelated changes don’t trigger repeat evaluation calls.For more information, visit Governance via Operator

Added TykSession CRD for declarative management of Sessions

A new TykSession custom resource lets you declare Sessions for API client credentials, such as API tokens and HTTP Basic Auth users, as Kubernetes resources. The Operator creates, updates, and revokes the corresponding Session in the Gateway as the resource changes. Policies associated with the Session (declared using the existing SecurityPolicy CRD) are referenced by their Kubernetes metadata.name, consistent with the Operator’s existing cross-resource reference model, so no raw Tyk IDs are needed in the manifest.

Added TykCertificate CRD for declarative TLS certificate management

A new TykCertificate custom resource uploads a TLS certificate from a same-namespace Kubernetes Secret into Tyk Certificate Store. The resulting certificate ID, fingerprint, and expiry are exposed on .status. The certificate ID is deterministic, so re-applying an unchanged resource is a no-op. Deleting the resource checks whether any API still depends on the certificate before removing it, so a certificate shared across multiple APIs is never deleted out from under them.

Added automatic reconciliation for externally rotated certificates and basic auth passwords

Operator detects when a Kubernetes Secret referenced by a TykCertificate or Basic Auth TykSession resource is rotated by an external system such as cert-manager or Vault, and reconciles the change automatically without needing a manual edit to trigger a sync. For certificates, a rotated Secret produces a new certificate in Tyk, uploaded before the old one is removed, and the old certificate is only cleaned up once nothing still depends on it, so a live API is never left pointing at a missing certificate.For Basic Auth passwords, rotation updates the credential in place in the same Session object, so quota and rate-limit counters are preserved.

Referencing a certificate or Session by its Kubernetes Secret name (rather than a copied-out Tyk ID) is what keeps it rotation-safe. A literal ID reference continues to work but won’t pick up future rotations automatically. Rotating the token/seed of a bring-your-own key isn’t supported, since the seed is the key’s identity; the Operator reports this as failed and recommends deleting and re-applying the resource instead.

Added TykIdentityProfile CRD for declarative TIB profile management

A new TykIdentityProfile custom resource lets you declare Tyk Identity Broker (TIB) profiles, which broker external identity providers for SSO into Tyk Dashboard, as Kubernetes resources. A profile is owned by either the Operator or the Dashboard, never both: an Operator-managed profile is authoritative, and any manual Dashboard edit is treated as drift and overwritten on the next reconcile, while a profile already created in the Dashboard is left alone unless explicitly annotated for the Operator to adopt it.Provider secrets in the profile configuration can be supplied as a reference to a same-namespace Kubernetes Secret rather than inline; the resolved value is sent to Tyk but never stored in the resource’s status, logs, or events, and rotating the referenced Secret automatically re-triggers reconciliation.

Added TykOAuthClient CRD for declarative Tyk OAuth 2.0 client management

A new TykOAuthClient custom resource lets you declare OAuth 2.0 clients bound to a specific Tyk OAuth 2.0 enabled API as Kubernetes resources. A client can be created with a specific client_id/client_secret supplied via a Kubernetes Secret, or left for Tyk to generate; a Tyk-generated client_secret is written to an Operator-owned Secret and never exposed in the resource’s status, logs, or events.

Added TykWebhook CRD for declarative webhook management

A new TykWebhook custom resource lets you declare global webhooks that can be triggered by Gateway events as Kubernetes resources. Header values can reference a same-namespace Kubernetes Secret instead of being set inline, so credentials sent to the webhook target are never stored in the resource’s status, logs, or events; rotating the referenced Secret automatically re-syncs the webhook.

Added TykUserGroup CRD for declarative Dashboard user group management

A new TykUserGroup custom resource lets you declare Dashboard user groups, the permission sets referenced by Dashboard users, TIB profiles, and Tyk OAS API ownership, as Kubernetes resources.

Added reconcile status and error reporting to the SecurityPolicy resource

SecurityPolicy resources now expose a status.latestTransaction field, matching the reconcile-status pattern already available on API definition resources. A failed Policy sync, an invalid Dashboard call or a missing linked API, is now visible directly on the resource via kubectl get securitypolicy, not just in the Operator’s logs. A transient Kubernetes conflict encountered while writing the status no longer causes a spurious “Failed” state to be reported.

API ownership is now applied for Tyk OAS APIs

The Tyk Operator now applies API ownership from OperatorContext to Tyk OAS APIs. user_owners and user_group_owners are applied on create and update, and updating these fields on an OperatorContext reconciles every Tyk OAS API that references it, keeping ownership consistent between Kubernetes and the Dashboard.

Security Fixes

Resolved CVEs

Addressed the following CVEs, providing increased protection against security vulnerabilities, including, but not limited to:

1.4 Release Notes

1.4.2 Release Notes

Release Date 9 July 2026

Release Highlights

In this release, we have fixed issues with the reliability of SecurityPolicy reconciliation under high load that could lead to infinite reconciliation loops, orphaned Dashboard policies, and inconsistent state between Kubernetes and Dashboard. The fix also introduces new configuration options that enable tuning of Tyk Operator’s HTTP connection pool for different deployments. For a comprehensive list of changes, please refer to the detailed changelog below.

Breaking Changes

This release has no breaking changes.

Dependencies

3rd Party Dependencies & Tools

Third Party Dependency	Tested Versions	Compatible Versions	Comments
Kubernetes	1.28.x to 1.35.x	1.19.x to 1.35.x

Deprecations

There are no deprecations in this release.

Upgrade instructions

Go to the Upgrading Tyk Operator section for detailed upgrade instructions.

Downloads

Docker image v1.4.2
- docker pull tykio/tyk-operator:v1.4.2
Helm chart
- tyk-charts v5.3.0

Changelog

Fixed

Fix SecurityPolicy reconciliation race conditions and connection leaks under load

Resolved a set of related issues that prevented SecurityPolicy resources from reconciling reliably, particularly under high load or when a policy referenced a large number of APIs.Affected Operators could enter continuous reconciliation loops (most commonly with policies referencing nine or more APIs), leave a policy in the Dashboard after its Kubernetes resource had been deleted, repeatedly try to recreate a policy and fail with a “policy name already used” error, and steadily leak HTTP connections and file descriptors until the host exhausted its available ports.SecurityPolicy reconciliation is now idempotent and converges reliably: Kubernetes and Dashboard state stay consistent across create, update, and delete, the Operator recovers cleanly from partial failures, and HTTP connections are reused correctly so file descriptors no longer accumulate under sustained load. The same reconciliation improvements have been applied to Tyk OAS API definition resources.This release also introduces a set of environment variables for tuning the Operator’s HTTP client to the Dashboard: TYK_OPERATOR_HTTPCLIENTCONFIG_MAXIDLECONNS, TYK_OPERATOR_HTTPCLIENTCONFIG_MAXIDLECONNSPERHOST, TYK_OPERATOR_HTTPCLIENTCONFIG_MAXCONNSPERHOST, TYK_OPERATOR_HTTPCLIENTCONFIG_IDLECONNTIMEOUT, TYK_OPERATOR_HTTPCLIENTCONFIG_TLSHANDSHAKETIMEOUT, and TYK_OPERATOR_HTTPCLIENTCONFIG_TIMEOUT. Each ships with a sensible built-in default, and Tyk recommends leaving them unchanged unless your infrastructure has specific constraints, such as file descriptor exhaustion, that require tuning.

Security Fixes

Resolved CVEs

Addressed the following CVEs, providing increased protection against security vulnerabilities, including, but not limited to:

1.4.1 Release Notes

Release Date 21 May 2026

Release Highlights

In this release, we have addressed CVEs for enhanced security and performance. For a comprehensive list of changes, please refer to the detailed changelog below.

Breaking Changes

This release has no breaking changes.

Dependencies

3rd Party Dependencies & Tools

Third Party Dependency	Tested Versions	Compatible Versions	Comments
Kubernetes	1.28.x to 1.32.x	1.19.x to 1.32.x

Deprecations

There are no deprecations in this release.

Upgrade instructions

Go to the Upgrading Tyk Operator section for detailed upgrade instructions.

Downloads

Docker image v1.4.1
- docker pull tykio/tyk-operator:v1.4.1
Helm chart
- tyk-charts v5.2.0

Changelog

Security Fixes

Resolved CVEs

Addressed the following CVEs, providing increased protection against security vulnerabilities, including, but not limited to:

1.4.0 Release Notes

Release Date 20 May 2026

Release Highlights

Tyk Operator 1.4.0 introduces support for managing MCP (Model Context Protocol) Proxy definitions through Kubernetes custom resources. The new TykMcpProxyDefinition CRD allows you to manage MCP Proxies declaratively, and the SecurityPolicy CRD has been extended with MCP access rights for tool-based access control and per-primitive rate limiting. For a comprehensive list of changes, please refer to the detailed changelog.

The initial Helm chart for Operator 1.4.0 contained an installation bug. Please ensure you use Tyk Charts 5.2.0 or later to install Operator 1.4.0.

Breaking Changes

This release has no breaking changes.

Dependencies

3rd Party Dependencies & Tools

Third Party Dependency	Tested Versions	Compatible Versions	Comments
Kubernetes	1.28.x to 1.32.x	1.19.x to 1.32.x

Deprecations

There are no deprecations in this release.

Upgrade instructions

The MCP Proxy support in Tyk Operator 1.4.0 requires Tyk Gateway 5.13.0 and Tyk Dashboard 5.13.0 (or newer) Attempting to use TykMcpProxyDefinition resources with Operator 1.4.0 prior to upgrading Gateway and Dashboard to a version supporting MCP Proxies will cause reconciliation failures. See MCP Gateway upgrade considerations for details. Go to the Upgrading Tyk Operator section for detailed upgrade instructions.

Downloads

Docker image v1.4.0
- docker pull tykio/tyk-operator:v1.4.0
Helm chart
- tyk-charts v5.2.0

Changelog

Added

Add MCP Proxy support

This release adds support for MCP (Model Context Protocol) Proxies with a new TykMcpProxyDefinition CRD and an extension to the SecurityPolicy CRD.TykMcpProxyDefinition CRDA new TykMcpProxyDefinition CRD allows you to manage MCP Proxy definitions declaratively in Kubernetes.The CRD status surface exposes three hashes — CRDSpecHash, ConfigMapHash, and TykSpecHash — to track synchronisation state between the Kubernetes resource, the ConfigMap, and the Tyk Gateway definition.SecurityPolicy CRD — MCP access rightsThe SecurityPolicy CRD has been extended to support MCP-specific access rights:

Per-tool, per-resource, and per-prompt allow/deny lists (mcp_access_rights)
Per-JSON-RPC-method allow/deny lists (json_rpc_methods_access_rights)
Per-primitive rate limits (mcp_primitives) and per-method rate limits (json_rpc_methods)

For details, see the MCP proxy policies documentation.

1.3 Release Notes

1.3.0 Release Notes

Release Date 11 March 2026

Release Highlights

Tyk Operator v1.3.0 delivers improvements for API monitoring and ingress management in Kubernetes environments. This release adds native uptime test configuration support for both Tyk OAS and Tyk Classic API definitions, eliminating the need for manual Dashboard configuration. For a comprehensive list of changes, please refer to the detailed changelog below.

The initial Helm chart for Operator 1.3.0 contained an installation bug. Please ensure you use tyk-charts version 5.1.1 or later to install Operator 1.3.0.

Breaking Changes

This release has no breaking changes.

Dependencies

3rd Party Dependencies & Tools

Third Party Dependency	Tested Versions	Compatible Versions	Comments
Kubernetes	1.28.x to 1.32.x	1.19.x to 1.32.x

Deprecations

There are no deprecations in this release.

Upgrade instructions

Go to the Upgrading Tyk Operator section for detailed upgrade instructions.

Downloads

Docker image v1.3.0
- docker pull tykio/tyk-operator:v1.3.0
Helm chart
- tyk-charts v5.1.0

Changelog

Changed

Golang 1.25 Update

The Tyk Operator now runs on Golang 1.25, providing improved performance, enhanced security, and access to the latest language features.This update ensures the Operator remains current with supported Go versions and reduces exposure to security vulnerabilities found in older runtime versions.

Added

Added Uptime Test Configuration Support

The Tyk Operator now supports configuration of upstream uptime tests directly in your API definitions through both Tyk OAS and Tyk Classic CRDs.

Fixed

Tyk Operator Ingress Controller Now Respects Strip Listen Path Configuration

The ingress controller now respects the listenPath.strip configuration defined in your Tyk OAS API templates. This fix ensures that template configurations are preserved while maintaining backward compatibility, as templates without an explicit strip setting will continue to default to true, and ACME challenge paths will still force strip: false as required.

1.2 Release Notes

1.2.0 Release Notes

Release Date 02 April 2025

Release Highlights

Support for Tyk 5.8

Tyk Operator v1.2 introduces key enhancements and critical fixes to improve API management in Kubernetes environments. This release adds support for HMAC request signing and YAML-based OAS definitions, aligning with Tyk Gateway 5.8. For a comprehensive list of changes, please refer to the detailed changelog below.

Breaking Changes

This release has no breaking changes.

Dependencies

3rd Party Dependencies & Tools

Third Party Dependency	Tested Versions	Compatible Versions	Comments
Kubernetes	1.28.x to 1.32.x	1.19.x to 1.32.x

Deprecations

There are no deprecations in this release.

Upgrade instructions

Tyk Operator v1.2 introduced new Custom Resource Definitions (CRDs). Before upgrading to Tyk Operator v1.2 with Helm Chart, please run the following commands to install the CRDs:

$ kubectl apply -f https://raw.githubusercontent.com/TykTechnologies/tyk-charts/refs/heads/main/tyk-operator-crds/crd-v1.2.0.yaml

Go to the Upgrading Tyk Operator section for detailed upgrade instructions.

Downloads

Docker image v1.2.0
- docker pull tykio/tyk-operator:v1.2.0
Helm chart
- tyk-charts v3.0.0

Changelog

Added

HMAC request signing support

Tyk Operator now supports HMAC request signing, enabling enhanced security and integrity for API requests. This feature aligns with Tyk 5.8 capabilities.Learn More

YAML-based OAS API definitions

Tyk Operator now allows OAS API definitions in YAML format, increasing flexibility in API configurations.

JWT OAS API policy linking

Tyk Operator now supports linking of policies for JWT default policies and JWT scope-to-policy mappings using kubernetes names. They can set these fields in TykOASApiDefinition CRD.

Updated

Show Removed dependency on kube-rbac-proxy

Tyk Operator removed dependency on kubebuilder’s rbac-proxy for authentication/authorization of metrics server. WithAuthenticationAndAuthorization feature provided by Controller-Runtime will be used instead.Users are encouraged to update to Tyk Operator v1.2 to benefit from this change.For users who cannot immediately update, there is an alternative option: modifying the Operator’s Helm chart configuration to replace the image gcr.io/kubebuilder/kube-rbac-proxy with another trusted source. For details, please see Issue 365.

Fixed

Operator reconciliation error handling

Fixed an issue where reconciliation conflicts appeared as errors in logs, which occurred because an outdated copy of the Kubernetes resource was being processed. This has been resolved by fetching the latest copy of the object from the cluster and retrying the operation.

Cert-manager dependency

Users can now disable cert-manager, making it optional rather than mandatory for onboarding. This enhances flexibility in deployment configurations.

Circuit breaker schema validation

Fixed an issue where user was getting validation error while setting threshold_precent field of classic API Definition CRD starting from Operator v1.0.0, which blocked users from upgrading.

Portal API Catalog infinite loop

Resolved an issue where the Operator could enter an infinite loop when a PortalAPICatalogue CR was created.

Leader election flag

Because of some issue in Operator helm chart, configurations options were not getting read correctly. Helm chart has been fixed and leader election works by default again.

1.1 Release Notes

1.1.0 Release Notes

Release Date 09 December 2024

Release Highlights

Support for Tyk Streams API

Tyk Operator v1.1 supports management of Tyk Streams APIs through the new TykStreamsApiDefinition custom resource. This allows you to have declarative, versioned, and fully automated control to your streaming APIs.

Breaking Changes

This release has no breaking changes.

Dependencies

3rd Party Dependencies & Tools

Third Party Dependency	Tested Versions	Compatible Versions	Comments
Kubernetes	1.26.x to 1.30.x	1.19.x to 1.30.x

Deprecations

There are no deprecations in this release.

Upgrade instructions

Tyk Operator v1.1 introduced new Custom Resource Definitions (CRDs). Before upgrading to Tyk Operator v1.1 with Helm Chart, please run the following commands to install the CRDs:

$ kubectl apply -f https://raw.githubusercontent.com/TykTechnologies/tyk-charts/refs/heads/main/tyk-operator-crds/crd-v1.1.0.yaml

Go to the Upgrading Tyk Operator section for detailed upgrade instructions.

Downloads

Docker image v1.1.0
- docker pull tykio/tyk-operator:v1.1.0
Helm chart
- tyk-charts v2.2.0

Changelog

Added

Show TykStreamsApiDefinition: new Custom Resource for Tyk Streams

The TykStreamsApiDefinition custom resource allows you to manage Tyk Streams APIs directly within your Kubernetes environment. This enhancement offers a Kubernetes-native approach to managing Tyk APIs, streamlining operations and ensure single source of truth in Kubernetes.Learn More

Fixed

Show SecurityPolicy: kind of referenced API definitions should have a default value

With TykOasApiDefinition support, we expect API references in SecurityPolicy to have kind field which can be either ApiDefinition or TykOasApiDefinition. However, the validation was failing if users were upgrading from v0.18 to v1.0 since the kind field is empty in the CR.Updated CRD rules to add default value for the kind field.

1.0 Release Notes

1.0.0 Release Notes

We are excited to announce the release of Tyk Operator v1.0, marking a significant milestone with new features, enhancements, and critical changes. This release introduces support for Tyk OAS APIs, extended capabilities for managing Classic APIs and security policies, and includes license changes that you must be aware of before upgrading.

Release Date 10 Oct 2024

Release Highlights

Support for Tyk OAS API

The Tyk Operator v1.0 release introduces powerful new features designed to enhance how you manage APIs in Kubernetes environments. One of the key highlights is the full support for Tyk OAS APIs, allowing you to define and manage APIs through the new TykOasApiDefinition custom resource. This integration extends GitOps API Management to Tyk OAS, allowing you to have declarative, versioned, and fully automated control to your APIs in Kubernetes environments. Key features:

Define and Manage Tyk OAS APIs using the TykOasApiDefinition custom resource.
Manage API Definitions in ConfigMaps: Any changes are automatically tracked and synced to Tyk.
Configure Tyk OAS in a Kubernetes-native way: You can organize APIs by categories or manage multiple API versions easily with the new CRD.
Simplify certificate management by referencing Kubernetes secrets.
Use the Tyk Ingress controller to create Tyk OAS APIs from Ingress specs.

With this release, users benefit from seamless GitOps workflows, ensuring a Kubernetes-native operation workflow. Security is also made simpler with automated certificate synchronization, removing the hassle of manual certificate management.

Enhanced Classic API and Security Policy Features

Enhanced support for Tyk Classic APIs continues, with improvements to security policies and new capabilities for setting API and endpoint-specific rate limits, making it easier than ever to customize API usage policies. This release represents a significant upgrade for both API management and security, offering a more efficient, scalable, and Kubernetes-native way to operate Tyk. Whether you’re leveraging Tyk OAS APIs or continuing with Tyk Classic, this version brings the tools and features you need to streamline your workflows and enhance operational efficiency. For details please refer to the changelog below.

Breaking Changes

License Requirement: Tyk Operator is now a closed-source product and requires a valid license key to operate. Please follow our Installation and Upgrade Guide to set your license key before installation or upgrade. If the license is missing, invalid, or expired, Tyk Operator will exit with an error message. Ensure that you carefully review the setup steps to avoid any issues during the upgrade or installation process. Admission Webhook Removal: The admission webhook for security policy (validate-tyk-tyk-io-v1alpha1-securitypolicy) has been removed. No action is required from users, and existing SecurityPolicy CRDs and resources remain fully supported and unaffected.

Dependencies

3rd Party Dependencies & Tools

Third Party Dependency	Tested Versions	Compatible Versions	Comments
Kubernetes	1.26.x to 1.30.x	1.19.x to 1.30.x

Deprecations

There are no deprecations in this release.

Upgrade instructions

Tyk Operator v1.0 introduced new Custom Resource Definitions (CRDs). Before upgrading to Tyk Operator v1.0 with Helm Chart, please run the following commands to install the CRDs:

$ kubectl apply -f https://raw.githubusercontent.com/TykTechnologies/tyk-charts/refs/heads/main/tyk-operator-crds/crd-v1.0.0.yaml

Go to the Upgrading Tyk Operator section for detailed upgrade instructions.

Downloads

Docker image v1.0.0
- docker pull tykio/tyk-operator:v1.0.0
Helm chart
- tyk-charts v2.1.0

Changelog

Added

TykOasApiDefinition: new Custom Resource for Tyk OAS

The TykOasApiDefinition custom resource allows you to manage Tyk OAS APIs directly within your Kubernetes environment. You can now categorize APIs, manage multiple versions, and simplify SSL certificate management by referencing Kubernetes secrets. This enhancement offers a Kubernetes-native approach to managing Tyk APIs, streamlining operations and reducing the complexity of versioning and certificate handling across different environments.Learn More: Create Tyk OAS API

Ingress Controller: Support Tyk OAS API as an Ingress Template

With this release, you can use the TykOasApiDefinition resource as a template for automatically creating Tyk OAS APIs based on Kubernetes Ingress specs. This simplifies the process of generating APIs by leveraging Ingress controller annotations, reducing manual intervention, and automating API creation workflows for better scalability and operational efficiency.Learn More: Tyk Ingress Controller

SecurityPolicy: Support for Key-Level Per-API Rate Limits and Quota

This release introduces the ability to configure specific rate limits, quotas, and throttling rules at the API level using the access_rights_array in the security policy. Each API now has the flexibility to inherit global limit settings or apply custom limits, making it easier to control API usage on a per-API basis. This provides enhanced granularity in managing traffic, ensuring optimal resource allocation and improved performance under heavy loads.Learn More: Key-Level Per-API Rate Limits and Quota

SecurityPolicy: Support for Key-Level Per-Endpoint Rate Limits

By configuring key-level per-endpoint limits, you can restrict the request rate for specific API clients to a specific endpoint of an API.Learn More: Key-Level Per-Endpoint Rate Limits

SecurityPolicy: Support for TykOasApiDefinition

This update extends the security policy to include TykOasApiDefinition resources within the access_rights_array, allowing you to manage security policies for both Tyk Classic APIs and Tyk OAS APIs. By specifying the API kind, you can now apply rate limits, quotas, and other access controls to Tyk OAS APIs, streamlining security management in mixed environments.Learn More: TykOasApiDefinition in Security Policy

ApiDefinition: Support for Event Handler

Tyk Operator now supports event handler integration for ApiDefinition, enabling webhooks to be triggered by specific API events. This allows for real-time, event-driven automation between Tyk and other systems, sending notifications or executing actions as events occur in the API lifecycle. The event_handlers field in the ApiDefinition CRD makes it easy to set up webhook-driven processes for better control and automation across your services.Learn More: Event Webhook with Tyk Classic

ApiDefinition: Support timeout Field in Advanced Cache Control

The advanced cache configuration for ApiDefinition now supports a timeout field, providing greater control over cache behavior. You can define specific cache timeouts for different API paths, allowing for more fine-tuned control over caching strategies. This feature helps optimize API performance, particularly for high-traffic endpoints requiring precise cache management.

extended_paths:
  advance_cache_config:
    - path: "/json"    
      method: "GET"
      cache_response_codes: [200, 204]
      timeout: 120

ApiDefinition: Support new Fields in VersionDefinition

VersionDefinition within ApiDefinition has been expanded to include additional fields, offering more granular control over API versioning and path management. These new fields allow you to configure version handling more flexibly, enhancing your ability to manage API versions and customize how version data is processed in API paths.

Changed

Show Go Version Updated to 1.22

The underlying Go runtime for Tyk Operator has been updated to version 1.22. This upgrade brings performance improvements, enhanced security, and compatibility with the latest Go libraries, ensuring Tyk Operator remains efficient and secure in production environments.

Show Admission Webhook for SecurityPolicy Removed

The admission webhook for the security policy (validate-tyk-tyk-io-v1alpha1-securitypolicy) has been removed because it did not perform any functional validation. This change simplifies deployment of Tyk Operator and reduces webhook overhead.

0.18 Release Notes

0.18.0 Release Notes

Release date 4 Jul 2024

Breaking Changes

This release has no breaking changes.

Deprecations

There are no deprecations in this release.

Upgrade Instructions

Go to the Upgrading Tyk Operator section for detailed upgrade instructions.

Release Highlights

This release added support for Tyk 5.4 API definition. For details please refer to the changelog below.

Downloads

Docker image v0.18.0
- docker pull tykio/tyk-operator:v0.18.0
Source code tarball - Tyk Operator Repo

Changelog

Added

Show Added support of Tyk 5.4 API definition CRD

Added to ApiDefinition Custom Resource Definition (CRD):

introspection option to enable/disable GraphQL introspection
graphql.proxy.auth_headers
graphql.proxy.subscription_type
graphql.proxy.request_headers
graphql.proxy.use_response_extensions
graphql.proxy.request_headers_rewrite
graphql.proxy.features

0.17 Release Notes

0.17.1 Release Notes

Release date 6 May 2024

Breaking Changes

This release has no breaking changes.

Deprecations

There are no deprecations in this release.

Upgrade Instructions

Go to the Upgrading Tyk Operator section for detailed upgrade instructions.

Release Highlights

This release is focused on bug fixes. For details please refer to the changelog below.

Downloads

Docker image v0.17
- docker pull tykio/tyk-operator:v0.17.1
Source code tarball - Tyk Operator Repo

Changelog

Fixed

Fixed ApiDefinition Custom Resources generated by the Ingress Controller used a wrong certificate

When using Tyk as an Ingress Controller with TLS enabled, the ApiDefinition Custom Resources generated by the Ingress Controller is missing the OrgID field. As a result, Tyk Gateway used a wrong certificate when serving a request. It is fixed by adding back OrgID field to ApiDefinition CRs created by Ingress Controller.

Added Webhook and RBAC port configurations in Tyk Operator Helm chart

Users can configure Tyk Operator webhook and RBAC port via helm chart values .Values.webhookPort and .Values.rbac.port respectively.

Addressed security vulnerabilities CVE-2023-45288

Addressed security vulnerabilities CVE-2023-45288 where an attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames. Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request’s headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed. This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send. The fix sets a limit on the amount of excess header frames we will process before closing a connection.

Addressed security vulnerabilities CVE-2024-24786

Addressed security vulnerabilities CVE-2024-24786 where the protojson.Unmarshal function can enter an infinite loop when unmarshaling certain forms of invalid JSON. This condition can occur when unmarshaling into a message which contains a google.protobuf.Any value, or when the UnmarshalOptions.DiscardUnknown option is set.

0.17.0 Release Notes

Release date 05 Apr 2024

Breaking Changes

This release has no breaking changes.

Deprecations

There are no deprecations in this release.

Upgrade Instructions

Go to the Upgrading Tyk Operator section for detailed upgrade Instructions.

Release Highlights

This release added support for GraphQLIntrospectionConfig in API definition and fixed an issue where the Tyk Operator creates duplicate APIs on Tyk. For details please refer to the changelog below.

Downloads

Docker image v0.17
- docker pull tykio/tyk-operator:v0.17.0
Source code tarball - Tyk Operator Repo

Changelog

Fixed

Show Fixed creating duplicated API definitions on Tyk

Fix creating duplicated API definitions on Tyk in case of cluster failures. If network errors happen while updating the API definition, the Tyk Operator retries the reconciliation based on the underlying error type.

Added

Show Added support of GraphQLIntrospectionConfig in API definition CRD

Added to ApiDefinition CRD: support of GraphQLIntrospectionConfig field at graphql.introspection.disabled. This feature will be enabled in future Tyk releases.

0.16 Release Notes

0.16.0 Release Notes

Release date 12 Jan 2024

Breaking Changes

This release has no breaking changes.

Deprecations

There are no deprecations in this release.

Upgrade Instructions

While upgrading Tyk Operator release via Helm, please make sure that the latest CRDs are also applied on the cluster, as follows:

kubectl apply -f https://raw.githubusercontent.com/TykTechnologies/tyk-operator/v0.16.0/helm/crds/crds.yaml

Release Highlights

This release added support for analytics plugin, UDG global header, and detailed tracing setting in ApiDefinition as detailed in the changelog below.

Downloads

Changelog

Added

Added imagePullSecrets configuration for ServiceAccount in Tyk Operator Helm chart

Added imagePullSecrets configuration for ServiceAccount in Tyk Operator Helm chart. It allows user to pull image from a private registry.

Added tyk to categories field of CRDs

Added tyk to categories field of CRDs. So, from now on, all CRs related to Tyk Operator is grouped into tyk category and can be displayed via kubectl get tyk.

Added support of analytics plugin in ApiDefinition CRD

Added to ApiDefinition CRD: support of analytics plugin at spec.analytics_plugin. See Example CRD with Analytics Plugin for details.

Added support of UDG Global Header in ApiDefinition CRD

Added to ApiDefinition CRD: support for UDG Global Header at spec.graphql.engine.global_headers object in ApiDefinition CRD. This feature is compatible with Tyk 5.2 or above.

Added support of detail tracing in ApiDefinition CRD

Added to ApiDefinition CRD: support for detail tracing configuration at spec.detailed_tracing field in ApiDefinition CRD. Enable it for the API if you want to get detail span for each middleware involved in request processing.

Updated

Show Updated Go version to 1.21

Updated Go version to 1.21

Fixed

Show Fixed CVE-2023-39325 (NVD)

Fixed CVE-2023-39325 (NVD)

Show Fixed security policy handling in OSS mode

Fixed a bug that prevents Tyk Operator to work with SecurityPolicy in OSS Mode. Now, SecurityPolicy controller will not modify spec.MID (_id) field in SecurityPolicy

Further Information

Upgrading Tyk

Please refer to the upgrading Tyk page for further guidance on the upgrade strategy.

FAQ

Please visit our Developer Support page for further information relating to reporting bugs, upgrading Tyk, technical support and how to contribute.

​Support Lifetime

​1.5 Release Notes

​1.5.0 Release Notes

​Release Date 23 September 2026

​Release Highlights

​Breaking Changes

​Dependencies

3rd Party Dependencies & Tools

​Deprecations

​Upgrade instructions

​Downloads

​Changelog

Changed

Added

Security Fixes

​1.4 Release Notes

​1.4.2 Release Notes

​Release Date 9 July 2026

​Release Highlights

​Breaking Changes

​Dependencies

3rd Party Dependencies & Tools

​Deprecations

​Upgrade instructions

​Downloads

​Changelog

Fixed

Security Fixes

​1.4.1 Release Notes

​Release Date 21 May 2026

​Release Highlights

​Breaking Changes

​Dependencies

3rd Party Dependencies & Tools

​Deprecations

​Upgrade instructions

​Downloads

​Changelog

Security Fixes

​1.4.0 Release Notes

​Release Date 20 May 2026

​Release Highlights

​Breaking Changes

​Dependencies

3rd Party Dependencies & Tools

​Deprecations

​Upgrade instructions

​Downloads

​Changelog

Added

​1.3 Release Notes

​1.3.0 Release Notes

​Release Date 11 March 2026

​Release Highlights

​Breaking Changes

​Dependencies

3rd Party Dependencies & Tools

​Deprecations

​Upgrade instructions

​Downloads

​Changelog

Changed

Added

Fixed

​1.2 Release Notes

​1.2.0 Release Notes

​Release Date 02 April 2025

​Release Highlights

Support for Tyk 5.8

​Breaking Changes

​Dependencies

3rd Party Dependencies & Tools

​Deprecations

​Upgrade instructions

​Downloads

​Changelog

Added

Updated

Fixed

​1.1 Release Notes

Support Lifetime

1.5 Release Notes

1.5.0 Release Notes

Release Date 23 September 2026

Release Highlights

Breaking Changes

Dependencies

Deprecations

Upgrade instructions

Downloads

Changelog

1.4 Release Notes

1.4.2 Release Notes

Release Date 9 July 2026

Release Highlights

Breaking Changes

Dependencies

Deprecations

Upgrade instructions

Downloads

Changelog

1.4.1 Release Notes

Release Date 21 May 2026

Release Highlights

Breaking Changes

Dependencies

Deprecations

Upgrade instructions

Downloads

Changelog

1.4.0 Release Notes

Release Date 20 May 2026

Release Highlights

Breaking Changes

Dependencies

Deprecations

Upgrade instructions

Downloads

Changelog

1.3 Release Notes

1.3.0 Release Notes

Release Date 11 March 2026

Release Highlights

Breaking Changes

Dependencies

Deprecations

Upgrade instructions

Downloads

Changelog

1.2 Release Notes

1.2.0 Release Notes

Release Date 02 April 2025

Release Highlights

Breaking Changes

Dependencies

Deprecations

Upgrade instructions

Downloads

Changelog

1.1 Release Notes

1.1.0 Release Notes

Release Date 09 December 2024

Release Highlights

Breaking Changes

Dependencies

Deprecations

Upgrade instructions

Downloads

Changelog

1.0 Release Notes

1.0.0 Release Notes

Release Date 10 Oct 2024

Release Highlights

Breaking Changes

Dependencies

Deprecations

Upgrade instructions

Downloads

Changelog

0.18 Release Notes