Skip to content

Releases: kubernetes/ingress-nginx

helm-chart-4.2.0

12 Jul 13:31
e222b74
Compare
Choose a tag to compare

Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer

NGINX Ingress Controller - v1.3.0 - The winter is coming

12 Jul 14:09
e222b74
Compare
Choose a tag to compare

Feature freeze

Hello ingress friends

This is going to be our last release before we enter into the feature freeze stabilization period we announced. Ingress wont have new features for the next 6 months. We will make releases only if bugfixes are required, and over v1.3.1!

If you have any questions, reach us in #ingress-nginx-users in Kubernetes Slack!

Important Changes

  • This release removes support for Kubernetes v1.19.0
  • This release adds support for Kubernetes v1.24.0
  • Starting with this release, we will need permissions on the coordination.k8s.io/leases resource for leaderelection lock

Image:

  • registry.k8s.io/ingress-nginx/controller:v1.3.0@sha256:d1707ca76d3b044ab8a28277a2466a02100ee9f58a86af1535a3edf9323ea1b5
  • registry.k8s.io/ingress-nginx/controller-chroot:v1.3.0@sha256:0fcb91216a22aae43b374fc2e6a03b8afe9e8c78cbf07a09d75636dc4ea3c191

KNOWN ISSUES:

  • This release reports a false positive on go-restful library that will be fixed with Kubernetes v1.25 release - Issue #8745

What's Changed

New Contributors

Full Changelog: controller-v1.2.1...controller-v1.3.0

helm-chart-4.1.4

10 Jun 11:02
96b6228
Compare
Choose a tag to compare

Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer

helm-chart-4.1.3

31 May 13:27
c32f9a4
Compare
Choose a tag to compare

Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer

controller-v1.2.1

31 May 13:58
c32f9a4
Compare
Choose a tag to compare

What's Changed

Image:

  • k8s.gcr.io/ingress-nginx/controller:v1.2.1@sha256:5516d103a9c2ecc4f026efbd4b40662ce22dc1f824fb129ed121460aaa5c47f8
  • k8s.gcr.io/ingress-nginx/controller-chroot:v1.2.1@sha256:d301551cf62bc3fb75c69fa56f7aa1d9e87b5079333adaf38afe84d9b7439355

This release removes the root and alias directives in NGINX, this can avoid some potential security attacks.

New Contributors

Full Changelog: controller-v1.2.0...controller-v1.2.1

helm-chart-4.1.2

24 May 00:05
6ea466b
Compare
Choose a tag to compare

Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer

helm-chart-4.1.1

10 May 16:14
61fcca3
Compare
Choose a tag to compare

Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer

helm-chart-4.1.0

22 Apr 02:37
6d9a39e
Compare
Choose a tag to compare

Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer

NGINX Ingress Controller - v1.2.0

22 Apr 02:44
6d9a39e
Compare
Choose a tag to compare

The chroot release :)

If you want to take full advantage of the security improvements in this release, and also want to take a look into the chroot feature, change the image in your manifest to use controller-chroot:v1.2.0 image and add the SYS_CHROOT capability.

We are going to release soon a blog post about this release!

Images:

  • k8s.gcr.io/ingress-nginx/controller:v1.2.0@sha256:d8196e3bc1e72547c5dec66d6556c0ff92a23f6d0919b206be170bc90d5f9185
  • k8s.gcr.io/ingress-nginx/controller-chroot:v1.2.0@sha256:fb17f1700b77d4fcc52ca6f83ffc2821861ae887dbb87149cf5cbc52bea425e5

This new release contains the following changes that need attention:

  • A new deep inspector for objects. Now every time an object gets to be reconciled/added, it will pass entirely through a validation (this may lead to some CPU increase)
  • The NGINX process now can be chrooted/jailed inside the ingress container, for security reasons. This option is disabled by default and will be enabled in future releases. This new option requires the SYS_CHROOT capability to be added to the Pod

What's Changed

New Contributors

Full Changelog: controller-v1.1.3...controller-v1.2.0

Thank you all for our amazing community!

helm-chart-4.1.0-beta.1

17 Apr 20:21
ef0ec5f
Compare
Choose a tag to compare
Pre-release

Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer