Kong Ingress Controller 0.3.0 released


#1

Kong Ingress Controller 0.3.0 has been release and is available for download.

0.3.0 brings support to use Kong 1.0 for Kubernetes Ingress along with enhancements to enable using multiple Kong clusters in one Kubernetes cluster.

Checkout the 0.3.0 Changelog for details.
Get started with using Kong for Ingress of your Kubernetes clusters today!


#2

Great news! we moved from 0.2.2 to 0.3.0 today , and we are using kong v1.0.0-alpine moved from 0.14.1, but we are getting errors in kong-ingress-controller:
I0110 10:49:28.510073 6 controller.go:128] syncing Ingress configuration… I0110 10:49:28.528584 6 kong.go:1075] cert: 0xc000047a90 E0110 10:49:28.532580 6 kong.go:209] err fetching upstream mock-http-server.8080 from Kong: json: cannot unmarshal number 1545238185.15 into Go struct field Upstream.created_at of type int64 E0110 10:49:28.532655 6 controller.go:131] unexpected failure updating Kong configuration: syncing targets: json: cannot unmarshal number 1545238185.15 into Go struct field Upstream.created_at of type int64


#3

Hey @pgold30,

Could you please open a Github issue for this? Please mention details on how you did the upgrade and share your relevant manifests. Thanks!


#4

I see that you’d already opened an issue:

Please do not cross post here and Github as it complicates tracking and organizing.
I’ve replied to the issue, let’s continue the conversation there. Thanks you for the report!