Here you will find information about migrating from a custom API gateway implementation based on the Spring Cloud Gateway OSS project to the commercial Spring Cloud Gateway for Kubernetes solution. Here are some things to consider:
- Can you leverage the commercial filters and predicates in place of your custom implementations?
- How can the custom filters and predicates you need for specific use cases get loaded into API gateway instances?
Migrate to commercial extensions
Spring Cloud Gateway for Kubernetes has released a number of commercial filters and predicates over its lifetime. Some of these commercial extensions have been migrated into the OSS project. There are still some commercial-only extensions that you should consider when migrating from an OSS implementation to the commercial solution.
By utilizing these commercial extensions, you could reduce the amount of custom code that needs to be maintained.
Custom extensions
When there are use cases in your OSS implementation that are not covered by existing commercial extensions, there is a need to migrate your custom filters and predicates for use in API gateway instances. In order to do this migration, you must package your custom extensions so they can be loaded into your API gateway instance. Please ensure your extensions are compatible with the Spring Cloud Gateway for Kubernetes runtime. See the Spring Cloud Gateway for Kubernetes Runtime description for Extensions developers under the product page for the full listing. Also, you should consider whether these commercial route filters could be useful for your custom extensions.
