Tyk Operator for Kubernetes
Tyk Operator v0.17.1 has been released
For a complete list of changes, please refer to the full changelog.
Updated:
Fixed:
Tyk Operator v0.16.0 added support for analytics plugin, UDG global header, and detailed tracing setting in ApiDefinition. See ApiDefinition CRD for the latest documentation.
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
imagePullSecrets
configuration for ServiceAccount in Tyk Operator Helm chartkubectl get tyk
.spec.analytics_plugin
. See Example CRD with Analytics Plugin for details.spec.graphql.engine.global_headers
object in ApiDefinition CRD.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.spec.MID (_id)
field in SecurityPolicy.Please see our version compatibility matrix
Fixed
Fixed 2 CVEs: GO-2023-1988, CVE-2023-3978
Fixed typo in environment package
Fixed linter issues that were raised after updating the package.
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
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.
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
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
ApiDefinition CRD is updated - it includes new fields in Status. Please update CRDs before upgrading to v0.14.2
kubectl apply -f https://raw.githubusercontent.com/TykTechnologies/tyk-operator/v0.14.2/helm/crds/crds.yaml
Full Changelog: https://github.com/TykTechnologies/tyk-operator/compare/v0.14.1...v0.14.2
Tyk Gateway and Dashboard v3.2, v4.0, v4.3, v5.0 Kubernetes version v1.20.15, v1.21.14, v1.22.15, v1.23.12, v1.24.6, v1.25.2, v1.26.3
e.g. docker run -it --rm --env-file=.env -v "$(pwd)":/dist tykio/tyk-operator:{tag} [FLAGS]
--category
flag with --separate
flag, so you can export API definitions from one category and Policies into separate files.For details, please refer to updated snapshot documentation here.
delete
method of ApiDefinition to handle unexpected status responses (500) from older version of Tyk Gateway while deleting non-existent APIs.update
method of ApiDefinition to handle update of a non-existent API. If ApiDefinition does not exist in Tyk, Operator will create it; otherwise, Operator will update it.We have updated the control-plane labels from controller-manager
to tyk-operator-controller-manager
. It is to avoid selector issues if you are running multiple controllers that was built with kubebuilder. In case of helm upgrade failure, please delete and install tyk-operator again.
Tyk Gateway and Dashboard v3.2, v4.0, v4.3, v5.0 Kubernetes version v1.19.16, v1.20.15, v1.21.14, v1.22.15, v1.23.12, v1.24.6, v1.25.2
allowed_types
or restricted_types
), and enable/disable of introspection. Note allowed_types
and disable_introspection
requires Tyk v4.3 or later.