Here you will learn about changes and options to consider when migrating from using Spring Cloud Gateway for VMware Tanzu Application Service tile service to Spring Cloud Gateway for Kubernetes.
Mapping vs. service binding
In Tanzu Application Service, Spring Cloud Gateway tile services leverage the Service Broker API and service binding approach for applications to setup container network routing of requests to a service instance. Spring Cloud Gateway for Kubernetes provides a SpringCloudGatewayMapping resource definition to expose API routes onto an API gateway instance.
See guide on SpringCloudGatewayMapping resource for more detailed information.
JSON vs. YAML API route configuration
The Spring Cloud Gateway tile service has a JSON based API route configuration approach. There are many similarities in terms of the configuration options available to those in Spring Cloud Gateway for Kubernetes. This section will go into detail about key differences.
Predicate configuration
API route configuration on Spring Cloud Gateway for Kubernetes does not provide top-level method and path configuration on per API route definition. Instead, you can define Method and Path predicates under the predicates array object. Please see Predicates section for more details.
Metadata timeouts
Instead of configuring connect-timeout and response-timeout under metadata, there is now the ability to configure these in the environment variables array object. Please see the example below:
spec:
...
env:
- name: spring.cloud.gateway.httpclient.connect-timeout
value: "1s"
- name: spring.cloud.gateway.httpclient.response-timeout
value: "5s"
...
Custom extensions support
Spring Cloud Gateway for Kubernetes provides the ability to load custom extensions into your API gateway instances. This is not available with Spring Cloud Gateway for VMware Tanzu tile and can activate additional use cases to be handled in your environment. Please see the section on how to develop your own custom extensions to learn more.
