# Kong Ingress Controller 0.3.0 released

**URL:** <https://discuss.konghq.com/t/kong-ingress-controller-0-3-0-released/2582>\
**Category:** General\
**Created:** [January 9, 2019, 6:37pm UTC](https://discuss.konghq.com/t/kong-ingress-controller-0-3-0-released/2582 "2019-01-09T18:37:52Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![hbagdi](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/hbagdi/32/562_2.png) [@hbagdi](https://discuss.konghq.com/u/hbagdi)\
**Post date:** [January 9, 2019, 6:37pm UTC](https://discuss.konghq.com/t/kong-ingress-controller-0-3-0-released/2582/1 "2019-01-09T18:37:52Z")

</div>

Kong Ingress Controller 0.3.0 has been release and is available for [download](https://bintray.com/kong/kubernetes-ingress-controller/kong-ingress-controller).

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](https://github.com/Kong/kubernetes-ingress-controller/blob/master/CHANGELOG.md#030---20190108) for details.  
[Get started](https://github.com/Kong/kubernetes-ingress-controller/blob/master/deploy/README.md) with using Kong for Ingress of your Kubernetes clusters today!

---

<div class="post-metadata">

**Author:** ![pgold30](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/pgold30/32/943_2.png) [@pgold30](https://discuss.konghq.com/u/pgold30)\
**Post date:** [January 10, 2019, 11:06am UTC](https://discuss.konghq.com/t/kong-ingress-controller-0-3-0-released/2582/2 "2019-01-10T11:06:00Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![hbagdi](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/hbagdi/32/562_2.png) [@hbagdi](https://discuss.konghq.com/u/hbagdi)\
**Post date:** [January 10, 2019, 4:39pm UTC](https://discuss.konghq.com/t/kong-ingress-controller-0-3-0-released/2582/3 "2019-01-10T16:39:58Z")

</div>

Hey @pgold30,

Could you please open a [Github issue](https://github.com/Kong/kubernetes-ingress-controller/issues/new) for this? Please mention details on how you did the upgrade and share your relevant manifests. Thanks!

---

<div class="post-metadata">

**Author:** ![hbagdi](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/hbagdi/32/562_2.png) [@hbagdi](https://discuss.konghq.com/u/hbagdi)\
**Post date:** [January 10, 2019, 6:30pm UTC](https://discuss.konghq.com/t/kong-ingress-controller-0-3-0-released/2582/4 "2019-01-10T18:30:34Z")

</div>

I see that you’d already opened an issue:

> <https://github.com/Kong/kubernetes-ingress-controller/issues/221>

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!