Kong gateway reaches 1.0 GA, now supports service mesh

#1

Post by hisham_hm » Thu, Dec 20, 2018, 6:01 PM UTC

Kong gateway reaches 1.0 GA, now supports service mesh
konghq.com

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#2

Post by aloisbarreras » Thu, Dec 20, 2018, 6:23 PM UTC

Great work guys! I see that "Kong’s core router can now route raw TCP traffic."

Can you elaborate? What kinds of routing parameters and rules can Kong use to route raw TCP traffic?

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#3

Post by fosk » Thu, Dec 20, 2018, 6:34 PM UTC

aloisbarreras wrote: post #2

Great work guys! I see that "Kong’s core router can now route raw TCP traffic." Can you elaborate? What kinds of routing parameters and rules can Kong use to route raw TCP traffic?

Since we now support Service Mesh, any TCP traffic is supported. The full documentation can be found at https://docs.konghq.com/

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#4

Post by hisham_hm » Thu, Dec 20, 2018, 6:43 PM UTC

aloisbarreras wrote: post #2

Great work guys! I see that "Kong’s core router can now route raw TCP traffic." Can you elaborate? What kinds of routing parameters and rules can Kong use to route raw TCP traffic?

You can define a route to be either L7 ("http", "https") or L4 ("tcp", "tls"). For L7 routes you can use the usual routing parameters that were already available in Kong, like routing by host, by paths (prefix or regex-based) and/or by method. For stream routing, you can route by IP source port, IP destination port and/or by SNI in the case of TLS connections.

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#5

Post by Supermighty » Thu, Dec 20, 2018, 7:00 PM UTC

What would be the best way to deploy this with my application in Kubernetes?

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#6

Post by hrrsppd » Thu, Dec 20, 2018, 7:03 PM UTC

How does 1.0 handle database migrations?

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#7

Post by yolo42 » Thu, Dec 20, 2018, 7:08 PM UTC

Supermighty wrote: post #5

What would be the best way to deploy this with my application in Kubernetes?

There are a few options to deploy Kong as your API Gateway:

Kong can work as an Ingress Controller for your Kubernetes cluster and run plugins for your traffic at the Ingress layer. Refere to the repo for more details: https://github.com/kong/kubernetes-ingress-controller

You can simply deploy it as an application using the Helm chart: https://github.com/helm/charts/tree/master/stable/kong

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#8

Post by judithpatudith » Thu, Dec 20, 2018, 7:13 PM UTC

Supermighty wrote: post #5

What would be the best way to deploy this with my application in Kubernetes?

There's a helm chart for that :) https://github.com/helm/charts/tree/master/stable/kong

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#9

Post by mikejulietbravo » Thu, Dec 20, 2018, 7:14 PM UTC

hrrsppd wrote: post #6

How does 1.0 handle database migrations?

Check out the Upgrade Path here: https://github.com/Kong/kong/blob/master/UPGRADE.md

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#10

Post by yolo42 » Thu, Dec 20, 2018, 7:18 PM UTC

hrrsppd wrote: post #6

How does 1.0 handle database migrations?

Kong runs at a critical point in any infrastructure. Having any sort of downtime is usually unacceptable.

To avoid downtime due to Kong upgrades, Kong now supports a blue-green deployment method where for two Kong nodes of version A and version A+1 can run together at the same time as the upgrade is being rolled out, and then switching all traffic to A+1.