|
1 | 1 | # Table of Contents
|
2 | 2 |
|
| 3 | + - [0.2.1](#021-20181026) |
3 | 4 | - [0.1.1](#011-20180926)
|
4 | 5 | - [0.2.0](#020-20180921)
|
5 | 6 | - [0.1.0](#010-20180817)
|
6 | 7 | - [0.0.5](#005---20180602)
|
7 | 8 | - [0.0.4 and prior](#004-and-prior)
|
8 | 9 |
|
| 10 | +## [0.2.1] - 2018/10/26 |
| 11 | + |
| 12 | +#### Added |
| 13 | + |
| 14 | + - **Header Injection in requests to Kong's Admin API** HTTP Headers |
| 15 | + can be set via CLI which will be injected in every request sent to |
| 16 | + Kong's Admin API, enabling the use of Ingress Controller when Kong's |
| 17 | + Control Plane is protected by Authentication/Authorization. |
| 18 | + [#172](https://github.com/Kong/kubernetes-ingress-controller/pull/172) |
| 19 | + - **Path only based routing** Path only Ingress rules (without a host) |
| 20 | + are now parsed and served correctly. |
| 21 | + [#142](https://github.com/Kong/kubernetes-ingress-controller/pull/142) |
| 22 | + - Under the hood, an external library is now used to talk to Kong's Admin |
| 23 | + API. Several other packages and dead code has been dropped. These changes |
| 24 | + don't have any user facing changes but are steps in direction to simplify |
| 25 | + code and make it more testable. |
| 26 | + [#150](https://github.com/Kong/kubernetes-ingress-controller/pull/150) |
| 27 | + [#154](https://github.com/Kong/kubernetes-ingress-controller/pull/154) |
| 28 | + [#179](https://github.com/Kong/kubernetes-ingress-controller/pull/179) |
| 29 | + |
| 30 | +#### Fixed |
| 31 | + |
| 32 | + - Fixed KongIngress overrides to enable overriding hashing attributes in |
| 33 | + Upstream object in Kong. |
| 34 | + Thanks @jdevalk2 for the patch! |
| 35 | + [#139](https://github.com/Kong/kubernetes-ingress-controller/pull/139) |
| 36 | + - Remove and sync certificates correctly when TLS secret reference changes |
| 37 | + for a hostname in Ingress spec. |
| 38 | + [#169](https://github.com/Kong/kubernetes-ingress-controller/pull/169) |
| 39 | + - Migrations for Kong are run using 'Job' in Kubernetes to avoid any |
| 40 | + issues that might arise due to multiple Kong nodes running migrations. |
| 41 | + [#161](https://github.com/Kong/kubernetes-ingress-controller/pull/161) |
| 42 | + - Kong and Ingress controller now wait for Postgres to start and migrations |
| 43 | + to finish before attempting to start. |
| 44 | + [#168](https://github.com/Kong/kubernetes-ingress-controller/pull/168) |
| 45 | + |
| 46 | + |
9 | 47 | ## [0.1.1] - 2018/09/26
|
10 | 48 |
|
11 | 49 | #### Fixed
|
|
102 | 140 | - The initial versions rapidly were iterated delivering
|
103 | 141 | a working ingress controller.
|
104 | 142 |
|
| 143 | +[0.2.1]: https://github.com/kong/kubernetes-ingress-controller/compare/0.2.0...0.2.1 |
105 | 144 | [0.1.1]: https://github.com/kong/kubernetes-ingress-controller/compare/0.1.0...0.1.1
|
106 | 145 | [0.2.0]: https://github.com/kong/kubernetes-ingress-controller/compare/0.1.0...0.2.0
|
107 | 146 | [0.1.0]: https://github.com/kong/kubernetes-ingress-controller/compare/v0.0.5...0.1.0
|
|
0 commit comments