List view
- No due date
- No due date
- No due date•18/18 issues closed
- Overdue by 9 month(s)•Due by August 26, 2024•59/59 issues closed
- Overdue by 1 year(s)•Due by June 10, 2024•164/164 issues closed
- No due date•157/157 issues closed
- No due date•71/71 issues closed
- No due date
- No due date•104/104 issues closed
A patch release including fixes for `CombinedRoutes`.
No due date•8/8 issues closed- No due date•116/116 issues closed
- Single controller deployments - a feature-gated version of the integration with Koko - surfacing `POST /config` errors as Kubernetes events - gRPC support for Gateway API - stretch/opportunistic: bump GWAPI to 0.6
No due date•143/143 issues closed- No due date•1/1 issues closed
- No due date•78/78 issues closed
This major release of the ingress controller is intended to enable several new features and allow for large (and in some cases backwards-incompatible) changes.
No due date•150/150 issues closed- No due date•33/33 issues closed
- Overdue by 2 year(s)•Due by September 26, 2022•7/7 issues closed
Gateway API items not assigned to a KIC release yet.
No due date•5/5 issues closed- Overdue by 2 year(s)•Due by September 15, 2022•30/30 issues closed
The intention of this milestone is to take our Gateway API implementation and move it to a beta maturity state where it is available by default in upcoming releases of the KIC and has documentation present in https://docs.konghq.com.
Overdue by 2 year(s)•Due by September 15, 2022•22/22 issues closed- Overdue by 3 year(s)•Due by June 10, 2022•4/4 issues closed
- No due date•10/10 issues closed
- Overdue by 3 year(s)•Due by February 24, 2022•4/4 issues closed
This milestone covers initial support for [Gateway APIs](https://github.com/kubernetes-sigs/gateway-api) according to our [Milestone 2 Definition](https://github.com/Kong/kubernetes-ingress-controller/blob/main/keps/0002-kong-gateway-api.md#milestone-2---alpha-quality---extended-api-support-provisional) in the relevant [KEP](https://github.com/Kong/kubernetes-ingress-controller/blob/main/keps/0002-kong-gateway-api.md).
No due date•26/26 issues closedThis milestone covers initial support for [Gateway APIs](https://github.com/kubernetes-sigs/gateway-api) according to our [Milestone 1 Definition](https://github.com/Kong/kubernetes-ingress-controller/blob/main/keps/0002-kong-gateway-api.md#milestone-1---alpha-quality---initial-http-support-implementable) in the relevant [KEP](https://github.com/Kong/kubernetes-ingress-controller/blob/main/keps/0002-kong-gateway-api.md).
No due date•26/26 issues closed- No due date•10/10 issues closed
- No due date•51/51 issues closed
- No due date•49/49 issues closed
- No due date•74/74 issues closed
In [upstream][kong] `v2.2.x` support for UDP was added, the purpose of this milestone is to track adding this feature to KIC. [kong]:https://github.com/kong/kong
No due date•4/4 issues closed**NOTE**: replaced by https://github.com/Kong/kubernetes-ingress-controller/milestone/21 Kubernetes upstream [Gateway API][gate] represents the upcoming standard which will most likely follow up and supersede [Ingress][ing]. The purpose of this milestone is to collect and track the work needed for an initial implementation of [v0.2.0][ver] that we can share with the community. [gate]:https://github.com/kubernetes-sigs/gateway-api [ing]:https://kubernetes.io/docs/concepts/services-networking/ingress/ [ver]:https://github.com/kubernetes-sigs/gateway-api/releases/tag/v0.2.0
No due date•5/5 issues closedPre-requisites: - [Kong Kubernetes Ingress Controller (KIC) 2.0-alpha.1](https://github.com/Kong/kubernetes-ingress-controller/milestone/15) - [Kong Kubernetes Testing Framework (KTF) v0.1.0](https://github.com/Kong/kubernetes-testing-framework/milestone/1) Historical KIC architecture had it's roots in older tooling and concepts around Kubernetes controller structure from several years prior and was missing a lot of newer context and functionality. As it relates to [KEP1][kep1] KIC 2.0 is the effort that started as a spike to re-architect the KIC while investigating #702. The purpose of this milestone is to **re-architect the KIC for simplified maintenance, paying back technical debt and to make it easier to contribute and add features going forward**, while keeping backwards compatibility as much as feasible. Follow up items which aren't making it into KIC 2.0 GA are in: - https://github.com/Kong/kubernetes-ingress-controller/milestone/17 [kep1]:https://github.com/Kong/keps/blob/main/keps/0001-single-kic-multi-gateway.md
No due date•119/119 issues closed- No due date
- No due date•2/2 issues closed
- No due date•15/15 issues closed
- No due date•7/7 issues closed
- No due date•12/12 issues closed
- Overdue by 4 year(s)•Due by August 28, 2020•35/35 issues closed
- No due date•3/3 issues closed
- Overdue by 5 year(s)•Due by January 6, 2020•8/8 issues closed
- Overdue by 5 year(s)•Due by September 16, 2019•7/7 issues closed
- No due date•10/10 issues closed