@@ -7,6 +7,7 @@ Adding a new version? You'll need three changes:
7
7
* Add the diff link, like "[2.7.0]: https://github.com/kong/kubernetes-ingress-controller/compare/v1.2.2...v1.2.3".
8
8
This is all the way at the bottom. It's the thing we always forget.
9
9
--->
10
+ - [ 2.10.0] ( #2100 )
10
11
- [ 2.9.3] ( #293 )
11
12
- [ 2.9.2] ( #292 )
12
13
- [ 2.9.1] ( #291 )
@@ -68,10 +69,14 @@ Adding a new version? You'll need three changes:
68
69
69
70
## Unreleased
70
71
72
+ ## [ 2.10.0]
73
+
74
+ > Release date: 2023-06-02
75
+
71
76
### Added
72
77
73
78
- Gateways now track UDP Listener status when ` --publish-service-udp ` is set.
74
- UDPRoutes that do not match a valid UDP Listener are excluded from
79
+ ` UDPRoute ` s that do not match a valid UDP Listener are excluded from
75
80
configuration. Previously KIC added any UDPRoute that indicated an associated
76
81
Gateway as its parent regardless of Listener configuration or status.
77
82
[ #3832 ] ( https://github.com/Kong/kubernetes-ingress-controller/pull/3832 )
@@ -172,23 +177,20 @@ Adding a new version? You'll need three changes:
172
177
173
178
- Kong Ingress Controller no longer relies on ` k8s.io.api.core.v1 ` ` Endpoints ` ,
174
179
and instead uses ` discovery.k8s.io/v1 ` ` EndpointSlice ` to discover endpoints
175
- for Kubernetes Services .
180
+ for Kubernetes ` Service ` s .
176
181
[ #3997 ] ( https://github.com/Kong/kubernetes-ingress-controller/pull/3997 )
177
- [ #3998 ] ( https://github.com/Kong/kubernetes-ingress-controller/pull/3998 )
178
- [ #3980 ] ( https://github.com/Kong/kubernetes-ingress-controller/pull/3980 )
179
- [ #3977 ] ( https://github.com/Kong/kubernetes-ingress-controller/pull/3977 )
180
182
- Gateway Discovery now produces DNS names instead of IP addresses
181
183
[ #4044 ] ( https://github.com/Kong/kubernetes-ingress-controller/pull/4044 )
182
184
183
185
### Fixed
184
186
185
- - Fix paging in ` GetAdminAPIsForService ` which might have caused the controller
187
+ - Fixed paging in ` GetAdminAPIsForService ` which might have caused the controller
186
188
to only return the head of the list of Endpoints for Admin API service.
187
189
[ #3846 ] ( https://github.com/Kong/kubernetes-ingress-controller/pull/3846 )
188
190
- Fixed a race condition in the version-specific feature system.
189
191
[ #3852 ] ( https://github.com/Kong/kubernetes-ingress-controller/pull/3852 )
190
- - Fixed a missing reconciliation behavior for Admin API EndpointSlice reconciler
191
- when the EndpointSlice that we receive a reconciliation request for is already
192
+ - Fixed a missing reconciliation behavior for Admin API ` EndpointSlice ` reconciler
193
+ when the ` EndpointSlice ` that we receive a reconciliation request for is already
192
194
missing
193
195
[ #3889 ] ( https://github.com/Kong/kubernetes-ingress-controller/pull/3889 )
194
196
- Fixed leader election role manifest where ` "" ` and ` "coordination" ` API groups
@@ -2499,7 +2501,7 @@ Please read the changelog and test in your environment.
2499
2501
- The initial versions were rapildy iterated to deliver
2500
2502
a working ingress controller.
2501
2503
2502
-
2504
+ [ 2.10.0 ] : https://github.com/kong/kubernetes-ingress-controller/compare/v2.9.3...v2.10.0
2503
2505
[ 2.9.3 ] : https://github.com/kong/kubernetes-ingress-controller/compare/v2.9.2...v2.9.3
2504
2506
[ 2.9.2 ] : https://github.com/kong/kubernetes-ingress-controller/compare/v2.9.1...v2.9.2
2505
2507
[ 2.9.1 ] : https://github.com/kong/kubernetes-ingress-controller/compare/v2.9.0...v2.9.1
0 commit comments