v0.15.0

Overview/Highlights

Tyk Operator v0.15.0 helps you understand API reconciliation status with a new 'latestTransaction' status subresource in APIDefinition CRD. We have added support for validate_json disabled field, additional volume options, and improved monitoring via ServiceMonitor for Prometheus. Fixes include allowing null value for subgraphs' headers and reconciliation issues.

Upgrading to v0.15.0

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.15.0/helm/crds/crds.yaml

What’s Changed?

Added

• Added ‘latestTransaction’ status subresource in APIDefinition CRD which holds information about API reconciliation status. You can use this status field to understand reconciliation status like whether the latest transaction is successful, transaction time, and in case of failure, the error description.
• Support for validate_json disabled field in APIDefinition CRD.
• Added extraVolume and extraVolumeMounts options to the helm chart. It can be used to mount CA certs.
• Added serviceMonitor option to the helm chart. Enabling this would expose /metrics endpoint via serviceMonitor object for Prometheus.

Fixed

• Allow subgraphs' header field to take null values to prevent errors when using an output from snapshot tool. While exporting GraphQL ApiDefinitions in older versions of Tyk via snapshot tool, spec.graphql.supergraph.subgraphs[].headers field is encoded as null because in Tyk v4.0, this field is not introduced and recognised as null value.
• Fix TLS secret reconciliation failure if certificate was already uploaded on Tyk.
• Fix reconciliation errors “the object has been modified; please apply your changes to the latest version and try again” that was created inside the reconciliation loop

Compatibility Notes

Tested on Tyk 5.0 and Kubernetes v1.26.3, v1.25.2, v1.24.6, v1.23.12, v1.22.15, v1.21.14, v1.20.15