|
1 | 1 | # Table of Contents
|
2 | 2 |
|
| 3 | + - [0.4.0](#040---20190424) |
3 | 4 | - [0.3.0](#030---20190108)
|
4 | 5 | - [0.2.2](#022---20181109)
|
5 | 6 | - [0.1.3](#013---20181109)
|
|
11 | 12 | - [0.0.5](#005---20180602)
|
12 | 13 | - [0.0.4 and prior](#004-and-prior)
|
13 | 14 |
|
| 15 | +## [0.4.0] - 2019/04/24 |
| 16 | + |
| 17 | +#### Summary |
| 18 | + |
| 19 | +This release introduces support to run Kong as an Ingress Controller |
| 20 | +without a database! |
| 21 | +This release comes with major under the hood rewrites to fix numerous |
| 22 | +bugs and design issues in the codebase. Most of the syncing logic has |
| 23 | +now been ported over to [decK](http://github.com/hbagdi/deck). |
| 24 | + |
| 25 | +This release comes with a number of breaking changes. |
| 26 | +Please read the changelog and test in your environment. |
| 27 | + |
| 28 | +#### Breaking Changes |
| 29 | + |
| 30 | +- :warning: Annotation `<plugin-name>.plugin.konghq.com` |
| 31 | + (deprecatd in 0.2.0) is no longer supported. |
| 32 | +- :warning: `--default-backend-service` CLI flag is now removed. The default |
| 33 | + service will now be picked up from the default backend in the Ingress rules. |
| 34 | +- :warning: Service and Upstream entity overrides via KongIngress CRD are now |
| 35 | + supported only with `configuration.konghq.com` annotation on Kubernetes |
| 36 | + services. |
| 37 | + Route level overrides work same as before, |
| 38 | + using the `configuration.konghq.com` annotation on Ingress resources. |
| 39 | +- :warning: `strip_path` property of Routes in Kong is set to `true` by default. |
| 40 | +- :warning: `preserve_host` property of Routes in Kong is set to |
| 41 | + `true` by default. |
| 42 | +- Plugins created for a combination of Route and Consumer using `consumerRef` |
| 43 | + property in KongPlugin CRD are not supported anymore. This functionality |
| 44 | + will be added back in future |
| 45 | + via [#250](https://github.com/Kong/kubernetes-ingress-controller/issues/250). |
| 46 | +- Service and upstream Host name have changed from |
| 47 | + `namespace.service-name.port` to `service-name.namespace.svc`. |
| 48 | + |
| 49 | +#### Added |
| 50 | + |
| 51 | +- Ingress Controller now supports a DB-less deployment mode using Kong 1.1. |
| 52 | + [#244](https://github.com/Kong/kubernetes-ingress-controller/issues/244) |
| 53 | +- New `run_on` and `protocols` properties are added to KongPlugin CRD. |
| 54 | + These can be used to further tune behaviors of plugins |
| 55 | + in Service Mesh deployments. |
| 56 | +- New fields are added to KongIngress CRD to support HTTPS Active healthchecks. |
| 57 | +- Ingress Controller is now built using Go 1.12. |
| 58 | +- Default service, which handles all traffic that is not matched against |
| 59 | + any of the Ingress rules, is now configured using the default backend |
| 60 | + defined via the Ingress resources. |
| 61 | + |
| 62 | +#### Fixed |
| 63 | + |
| 64 | +- Logs to stdout and stderr will be much more quieter and helpful and won't |
| 65 | + be as verbose as before. |
| 66 | +- Routes with same path but different methods can now be created. |
| 67 | + [#202](https://github.com/Kong/kubernetes-ingress-controller/issues/202) |
| 68 | +- Removing a value in KongPlugin config will now correctly sync it to Kong. |
| 69 | + [#117](https://github.com/Kong/kubernetes-ingress-controller/issues/117) |
| 70 | +- Setting `--update-state=false` no longer causes a panic and performs leader |
| 71 | + election correctly. |
| 72 | + [#232](https://github.com/Kong/kubernetes-ingress-controller/issues/232) |
| 73 | + Thanks to [@lijiaocn](https://github.com/lijiaocn) for the fix!! |
| 74 | +- KongIngress will now correctly override properites of Upstream object |
| 75 | + in Kong. |
| 76 | + [#252](https://github.com/Kong/kubernetes-ingress-controller/issues/252) |
| 77 | +- Removing a value from KongPlugin config will now correctly unset it in |
| 78 | + Kong's datastore. |
| 79 | + [#117](https://github.com/Kong/kubernetes-ingress-controller/issues/117) |
| 80 | + |
| 81 | +#### Under the hood |
| 82 | + |
| 83 | +- Translation of Ingress rules and CRDs to Kong entities is completey |
| 84 | + re-written. |
| 85 | + [#241](https://github.com/Kong/kubernetes-ingress-controller/issues/241) |
| 86 | +- For database deployments, an external tool, decK is used to sync resources |
| 87 | + to Kong, fixing numerous bugs and making Ingress Controller code saner |
| 88 | + and easier to maintain. |
| 89 | + |
14 | 90 | ## [0.3.0] - 2019/01/08
|
15 | 91 |
|
16 | 92 | #### Breaking Changes
|
|
264 | 340 | - The initial versions rapidly were iterated delivering
|
265 | 341 | a working ingress controller.
|
266 | 342 |
|
| 343 | +[0.4.0]: https://github.com/kong/kubernetes-ingress-controller/compare/0.3.0...0.4.0 |
267 | 344 | [0.3.0]: https://github.com/kong/kubernetes-ingress-controller/compare/0.2.2...0.3.0
|
268 | 345 | [0.2.2]: https://github.com/kong/kubernetes-ingress-controller/compare/0.2.1...0.2.2
|
269 | 346 | [0.1.3]: https://github.com/kong/kubernetes-ingress-controller/compare/0.1.2...0.1.3
|
|
0 commit comments