@@ -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.9.2] ( #292 )
10
11
- [ 2.9.1] ( #291 )
11
12
- [ 2.9.0] ( #290 )
12
13
- [ 2.9.0-rc.1] ( #290-rc1 )
@@ -64,17 +65,25 @@ Adding a new version? You'll need three changes:
64
65
- [ 0.0.5] ( #005 )
65
66
- [ 0.0.4 and prior] ( #004-and-prior )
66
67
67
- ## [ 2.9.1 ]
68
+ ## [ 2.9.2 ]
68
69
69
- > Release date: 2023-03-29
70
+ > Release date: 2023-04-03
70
71
71
- ### Fixed
72
+ ### Fixed
72
73
73
74
- Fixed a deadlock in ` AdminAPIClientsManager ` which could occur when Konnect integration
74
75
was enabled, and multiple ` Notify ` calls were made in parallel (e.g. when scaling Gateway
75
76
deployment up).
76
77
[ #3816 ] ( https://github.com/Kong/kubernetes-ingress-controller/pull/3816 )
77
78
79
+ ## [ 2.9.1]
80
+
81
+ > Release date: 2023-03-29
82
+
83
+ This release was intended to include a fix for a deadlock in ` AdminAPIClientsManager `
84
+ ([ #3816 ] ( https://github.com/Kong/kubernetes-ingress-controller/pull/3816 ) ), but it wasn't
85
+ backported properly. It is included in the next patch release.
86
+
78
87
## [ 2.9.0]
79
88
80
89
> Release date: 2023-03-27
@@ -2336,6 +2345,7 @@ Please read the changelog and test in your environment.
2336
2345
- The initial versions were rapildy iterated to deliver
2337
2346
a working ingress controller.
2338
2347
2348
+ [ 2.9.2 ] : https://github.com/kong/kubernetes-ingress-controller/compare/v2.9.1...v2.9.2
2339
2349
[ 2.9.1 ] : https://github.com/kong/kubernetes-ingress-controller/compare/v2.9.0...v2.9.1
2340
2350
[ 2.9.0 ] : https://github.com/kong/kubernetes-ingress-controller/compare/v2.8.1...v2.9.0
2341
2351
[ 2.8.1 ] : https://github.com/kong/kubernetes-ingress-controller/compare/v2.8.0...v2.8.1
0 commit comments